otest -- only useful for bundles?
otest -- only useful for bundles?
- Subject: otest -- only useful for bundles?
- From: James Bucanek <email@hidden>
- Date: Sat, 5 Nov 2005 17:23:31 -0700
Greetings,
I wanted to add some Xcode 2.1 unit tests to a Objective-C command-line tool. Reading the Unit Testing docs, I see that one of build settings for a unit test target is the Test Host settings.
The documentation seems to hint that a "dependent" unit test can be configured to load the actual application executable as if it were a dynamic library, link the unit tests to that binary code, and execute the tests. This is referred to as "bundle injection."
However, the only example of doing this demonstrates using a bundled app with a TEST_HOST of $(BUILT_PRODUCTS_DIR)/MyApp.app/Contents/MacOS/MyApp. I've tried to set the TEST_HOST to my command-line executable at $(BUILT_PRODUCTS_DIR)/MyTool without success.
Does this technique only work for bundled apps? Is there some way of doing this for other kinds of executable products, or must I compile the code seperately in the unit test target? I can find no documentation for otest or the RunUnitTest scripts that explain how they load and execute their tests. I know it's supposed to "just work," but in this case I'm afraid I need to know.
--
James Bucanek
_______________________________________________
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