I was receiving the following error while trying to run my unit tests from XCode:

Test Host –path to app– exited abnormally with code 138

For whatever reason, removing the tests from the Unit Tests target and re adding them to the target made the error go away. No other changes necessary.

Here is the article that explains how to add unit testing to XCode 3 project.

http://developer.apple.com/mac/articles/tools/unittestingwithxcode3.html

If you search for unit testing with XCode you will find a lot of older articles pointing to XCode 2.x and how to install etc, etc. Now XCode 3 includes unit testing out of the box, so it is a lot simpler.

Came across an interesting problem. Trying to get distributed objects to pass a common class between processes.

To avoid versioning issues I had the class in a shared location so that both client and server could use it.

On the server I was seeing a decodeRetainedObject: class ‘bleh’ not loaded error in the console log. Took a while to figure out, but XCode doesn’t automatically assign a class that are dragged and dropped into a project to the main target. The files simply needed to be assigned to the requisite target and everything works fine.