Externally controlling BurnInTest |

Controlling BurnInTest from another application Users can run BurnInTest from an external controlling application using the BurnInTest command line options. This can be useful if BurnInTest testing is one of several steps in the system validation process and this process is to be controlled by another application. BurnInTest can run for a specified duration, number of cycles or run a scripted series of tests. The external application can also configure BurnInTest somewhat by creating a BurnInTest subscript file. A subscript file is a special BurnInTest script file that must be named "bit-script-input.txt" and placed in the BurnInTest program files directory prior to running BurnInTest. The subscript file must conform to the BurnInTest scripting syntax. This subscript file can contain "SET<XYZ> ..." scripting commands to set test configuration. BurnInTest will delete this subscript file once it has been run. For example, a batch file could be created to set the logging file and run BurnInTest: rm "%programfiles%/burnintest/bit-script-input.txt" echo SETLOG LOG yes NAME "C:\logs\BIT_Results_%COMPUTERNAME%.html" > "%programfiles%/burnintest/bit-script-input.txt" "%programfiles%/burnintest/bit.exe" There is an option with the licensed version of BurnInTest to allow the controlling application to stop the BurnInTest testing and BurnInTest can be configured to exit at the end of the testing. To allow an external application to signal BurnInTest testing to stop, BurnInTest must be started with the "-T" command line parameter. Once the tests are running the application controlling BurnInTest can signal BurnInTest to stop testing by creating a file called "BURNINTEST_STOP" in the BurnInTest program files directory or the '..\<UserName>\Documents\PassMark\BurnInTest\' directory, where <UserName> is the administrator account that BurnInTest is run under. The application that creates the stop file must delete this file. To configure BurnInTest to exit at the end of testing, specify Test Preferences->Post-Test 'Run external application and exit' and leave the application field blank. Controlling other applications from BurnInTest BurnInTest can run an external application (and wait for it to complete) before running tests. This can be used for a number of reasons such as changing the test environment before testing or having an external application provide test information to BurnInTest, such as the company name, tester's name, serial number etc. See Pre-Test preferences to see how an external application can pass a sub-script of commands to BurnInTest to configure test information such as the system serial number. BurnInTest can run external applications (and wait for it to complete) after running tests. This can be used for a number of reasons such as resetting the test environment after testing or passing results to another application to have it perform another step in the system validation process. To see how to run an application from BurnInTest after testing and what parameters (e.g. $RESULT) can be passed to this application please see Post-Test preferences.