# Test Preferences – Pre-Test

Action before running tests

You may specify the default behavior of BurnInTest before it begins any test cycle.

None (start immediately)

Immediately starts test(s) without any warning message or reminders.

Display warning message (default)

Displays the default warning message reminding the user of some basic precautions, such as possible port conflicts and the presence of loopback plugs and cables. Note: Pre-test warnings are not provided for Plugin tests.

Run external application

Run another application prior to starting the test run. For instance the user may wish to launch the Windows Performance Monitor to examine the effects of the test on the system.

Run external application &wait for it to exit (Passing configuration information from an external program to BurnInTest).

Run another application prior to starting the test run. BurnInTest will wait for this application to exit before it continues. On continuing, BurnInTest will check for a subscript file (see below). The executable file may produce a file of scripting commands that are to be run by BurnInTest once the executable file has closed. As an example, this may be used to set the Machine type, serial number, test notes etc at the start of each individual test run.

The only script commands that will be processed by BurnInTest are the SET… commands. All other commands will be ignored. If this file, called a subscript file, is created is must:

- be placed in the same directory as the application executable file;
- must be called “bit-script-input.txt”; and
- must conform to the scripting file format.

After processing the script commands in this file, BurnInTest will delete the file.

See also, EXECUTEWAIT

External Application

The path to the external application above.