• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Xcode 4 and unit tests
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Xcode 4 and unit tests


  • Subject: Re: Xcode 4 and unit tests
  • From: Logan Cautrell <email@hidden>
  • Date: Tue, 05 Apr 2011 13:37:07 -0500

Using GHUnit is much better and far simpler than Xcode's unit testing support. The test runner enables you to set breakpoints and debug your code just like running your applications. They also have support for running from the command line. Setting it up to run as part of a build process is straight forward.
    -logan

On Apr 1, 2011, at 5:15 PM, Paul Summermatter wrote:

> Mike,
>
> 	We haven't taken the plunge yet to Xcode 4, but I can say that Xcode has not had good support for unit testing, and it's been more than a little frustrating.  I'm used to IDEA where everything just works without much effort.  That being said, others on this list recommended using GHUnit, and we followed their advice and are much happier for it:
>
> http://gabriel.github.com/gh-unit/
>
> 	It's been a while since we made the switch, and I don't remember all the details of what we had to do, but I seem to recall it was relatively straightforward to set up.
>
> Regards,
> Paul
>
> On Apr 1, 2011, at 2:21 PM, McLaughlin, Michael P. wrote:
>
>> I delayed  installing Xcode 4 until it was released.  I now have Xcode 4.0.1
>> installed in parallel to Xcode 3.2.6.
>>
>> I am not very familiar with Xcode 4 nor with the unit testing mechanism it
>> uses.  Therefore, I set forth to remedy the latter situation.
>>
>> Hoping that it would “just work”, I created a new (non-document) Cocoa app
>> project with unit tests enabled and Git disabled.  Building for running
>> worked well and the app ran as expected.
>>
>> Building for testing failed with the error
>>
>> SenTestingKit/SenTestingKit.h file not found
>>
>> I saw that the SenTestingKit framework was not in the project but that its
>> header path was specified in the Build options.  Just to be sure, I added
>> this framework to the Other Frameworks group in the project.  The build for
>> testing still failed even when I added this framework to both targets.
>>
>> Nothing in the User Guide prepared me for this.  Am I missing something
>> obvious?
>>
>> Thanks.
>>
>> --
>> Mike McLaughlin
>>
>> _______________________________________________
>> Do not post admin requests to the list. They will be ignored.
>> Xcode-users mailing list      (email@hidden)
>> Help/Unsubscribe/Update your Subscription:
>>
>> This email sent to email@hidden
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Xcode-users mailing list      (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >Xcode 4 and unit tests (From: "McLaughlin, Michael P." <email@hidden>)
 >Re: Xcode 4 and unit tests (From: Paul Summermatter <email@hidden>)

  • Prev by Date: Passing non-string user defaults through command line arguments
  • Next by Date: Re: xcode 4 documentation when offline
  • Previous by thread: Re: Xcode 4 and unit tests
  • Next by thread: Xcode 3.2.6 keeps switching to iPad simulator
  • Index(es):
    • Date
    • Thread