Thanks so much!  You da man! 

Just a tip. You don’t need to modify the ‘Copy Bundle Resources’ build phase of your target to maintain separation of artwork between different targets.

An alternative method is to create subdirectories in your project root, then drag that folder into the Xcode ‘Groups & Files’ pane underneath the ‘Resources’ group.

Make sure ‘Copy items into destination’ is unchecked and the reference type is ‘Relative to Project’.

Then you can open the Info panel for each of these newly created groups and change the target membership to the correct target. Also ensure any resources inside each group have the correct target membership.

This way just feels cleaner to me.

I also prefer running my unit tests separately before checking in my code rather than every time during build – some of my tests involve file reading/writing and network stuff that slows down the execution.

Yes, I’m using UnitTest++ quite extensively with XCode and the iPhone and an article describing that is pretty high up in my priority list. Now I just need to find the time

I’m surprised you list running the unit tests as part of the build a disadvantage though. That’s how I run all of them. How’s your ideal set up? Do you run them as a separate step afterwards?

Because you mentioned test targets: I wonder if you could write an article about unit testing with XCode. Are you still developing/using UnitTest++?

I find unit testing in XCode quite a pain because you need to run the tests as part of the build process to be able to double-click on the error messages.