Previous Entry Share Next Entry
Xcode unit testing articles updated
I've updated my posts on creating and debugging unit tests for for Cocoa applications and frameworks for Xcode 3.0. If you have any additional questions about how unit testing works in Xcode, don't hesitate to ask!

Here are pointers to the updated articles:

The most significant change is in debugging Cocoa application unit tests. There's an extra environment variable you'll need to add to your executable, DYLD_FALLBACK_FRAMEWORK_PATH, before you'll be able to debug it with Xcode 3.0. This is necessary because Xcode takes advantage of a new linker feature — runpath-relative install names — in order to support moving and renaming your Developer folder and having multiple versions of Xcode installed.

  • 1
Bookmarking - need to find time to play with Xcode with some weekend again (on the same list with other todos like VS-O, VM-O, setting up Lab Manager, learning more perl, fixing the MacBook, cleaning a few TB storage and files...) so when I can relax I can do something so unlike work.. :p
(btw, can I add in linkedin? :)

architecture pain

Hi. I am compiling some code with the architecture set to x86_64. When I run /usr/bin/arch it replies i386. I'm on a macbook pro intel core 2 duo qith leopard, and that sounds 64 bit (am I wrong?)

I have some tests that are to be run from the sen testing script. I also run them from a main function on a target for debugging. When runned from the target every thing runs fine. When running from the script I get errors from tests that compare bytes read from a file. Looks like the test framework is assuming something 32 bit. I then set all the variables (ARCH, VALID_ARCHS, NATIVE_ARCH_ACTUAL) to the value x86_64, but the result is the same.

Do you have any idea to what might be happening ?

Re: architecture pain

Rather than asking me directly, please ask on xcode-users mailing list, and be sure to specify what version of Xcode you're using. That's the place to go for help with everything Xcode.

thank you

thanks much, brother

Trapping SenTestingKit messages/events with NSNotificationCenter

Hi Chris.

I posted this question ( on a while back about how one might trap the testCaseDidStart/testCaseDidStop messages in an OCUnit test bundle.

I want to reformat the messages emitted when tests pass/fail so I can integrate OCUnit with my continuous integration system. At the moment I'm just parsing the output from RunUnitTests with a perl script but I figure that there has got to be a better way.


Selecting the tests to run


Often, when running test cases and debugging them, I need to concentrate on just one. Is there any way of specifying the tests to be run ?

I currently use bundle injection and specify -SenTest All for running the script. What do I say instead of all ?

  • 1

Log in