I recommend that anyone who runs the unit tests regularly add this line to their setup file:
export CHANDLER_LAUNCH_TEST=1
One of our Tinderbox machines will be set up to run this test. Hopefully most of you will run this test as well.
DETAILS
-----------
The TestLaunchChandler test should not interfere with your normal repository; it creates a new repository in the same directory where the "debug" and "release" directories reside. You can override this placement by setting up the CHANDLER_LAUNCH_TEST_PROFILEDIR environment variable.
After Chandler is launched, a CPIA Script is automatically executed. For now the script is trivial, it just does a Quit, but soon we'll put in a more extensive script that will give Chandler a bit of a workout, creating and deleting Items, etc before quitting.
Running the test is a noop unless you have the CHANDLER_LAUNCH_TEST environment variable set up. The default is to NOT run the test so Tinderbox won't try to do so. The constrained environment used by Tinderbox can't launch applications, and has no environment variable settings, so we needed to default the test to "off". However, Bear has one machine that runs in a more expanded environment, so it does run the test. The bottom line; if you make a change that causes Chandler to be unable to launch, that problem should show up on one of the Tinderbox clients.
- Donn Denman
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list http://lists.osafoundation.org/mailman/listinfo/dev
