On Jul 15, 2005, at 12:54 AM, Amy wrote:
Using info gathered from this list and the instructions in Apple's Xcode 2.1 User Guide I created a
custom executable that points to otest and has the following settings:
General Pane:
executable path: /Developer/Tools/otest
working directory set to Build Products directory
Arguments Pane:
Arguments to be passed on launch are:
-SenTest All
AFramerworkTestTarget.octest
Variables to be set in the environment are:
DYLD_INSERT_LIBRARIES = /System/Library/PrivateFrameworks/DevToolsBundleInjection.framework/DevToolsBundleInjection
XCInjectBundle = $(BUILT_PRODUCTS_DIR)/AFramerworkTestTarget.octest
I think my instructions on the list earlier weren't completely clear, they were specific to debugging application unit tests.
If you want to debug framework unit tests, you'll want to specify these two environment variables instead of what you have above:
DYLD_FRAMEWORKPATH = $(BUILT_PRODUCTS_DIR)
DYLD_LIBRARY_PATH = $(BUILT_PRODUCTS_DIR)
This will tell the loader to search your build directory for frameworks & libraries to load before searching anywhere else, ensuring that the version of the framework you built is the one your tests will be run against.
-- Chris