Xcode - Debugging a unit test target

问题:

I am writing tests for my iPhone app using OCUnit. Is there any way to debug the unit tests and have a break point to see what the heck is happening?

It's ridiculously hard to write unit tests without being able to use breakpoints.

回答1:

The link posted by David Gelhar is correct for Xcode 3.

For Xcode 4, things are much simpler. Edit your current scheme and go to the "Test" action. Click the '+' at the bottom and add the test bundle that contains the tests you want to run. Now when you choose Product -> Test, it will run those tests. Any active breakpoints will be hit just like you'd expect.

回答2:

Using XCode 4.2, (with SenTestKit unit tests as set up by checking the "Include Unit Tests" checkbox when setting up the project), Product->Test wasn't hitting my breakpoints, but Product->Perform Action->Test Without Building seems to do the trick. Hope this helps.

回答3:

Here's a blog post: Debugging Cocoa application unit tests with instructions for how to do this (for XCode 3 at least; not sure about XCode 4).

回答4:

Another item to watch for in XCode 4 is that you haven't added the classes being tested to the Unit Test Target as well as the main project. It appears that it's not necessary and it will mess up your ability to have breakpoints hit.

A clue will be warning messages in the debug log when you run. The messages will look like this:

"Class XXX is implemented in both YYY and ZZZ. One of the two will be used. Which one is undefined."

Once I removed the classes noted in the warnings from the unit test target, Xcode started hitting the breakpoints.

You can remove classes from a target by clicking on the .M file, and turning off its membership in the unit test target in the inspector window under "Target Membership".