The Battery Test System requires use of the batch process model for executing test sequences in TestStand.

Note For guidance on using the batch process model, refer to Set Report Options for Long-Duration Tests for information on how to configure your TestStand report options.

Start a Test

Execute a sequence (run a test) in TestStand by selecting Tools » Configureand Run BTS Batch or Execute » Test UUTs from the menu bar. The Configure and Run BTS Batch closely simulates running the test from the Web UI. It shows the UUT options using 1-based socket numbers, only runs one batch of tests, and gives you the option to interactively change the input parameter values used by the test.

Refer to Executing Sequences in the TestStand Help for more information.

Note The Execute » Test UUTs dialog shows the UUT socket numbers as 0, 1, 2, and 3 for a 4-socket batch test. However, these execute as sockets 1, 2, 3, and 4 respectively wherever Batch socket numbers are evaluated in the test for a Battery Test System test.
Note When running a test in TestStand, each UUT execution tab shows the UUT socket numbers as 0, 1, 2, and 3 for a 4-socket batch test. However, these are actually executing sockets 1, 2, 3, and 4 respectively for Battery Test System tests.

Behavioral notes when initializing:

Note The projects mentioned in the notes that follow can refer to the VeriStand project or the VeriStand system definition file, whichever was configured in the Configure VeriStand Connection dialog.
  • When VeriStand is closed, VeriStand opens and attempts to deploy the project and waits for connection.
  • When VeriStand is open, but no project is deployed, VeriStand attempts to deploy the selected project.
  • When the VeriStand project is deployed, VeriStand does nothing.
  • When a different project is deployed on the gateway, VeriStand generates an error.
  • When the test sequence is run from the Web UI, the Test Executor, or from the Configure and Run BTS Batch menu option and a different project is deployed on the gateway, VeriStand attempts to undeploy the deployed project and then deploy the new selected project.
Note Initialization and closing of VeriStand is implemented as a process model plug-in. As such, initialization and closing of VeriStand only occurs in situations in which process model plug-ins are called (such as Single Pass and TestUUT(s) entry points of the default process models, but not if running selected steps in a sequence).

Debug a Test

Refer to Debugging Executions in the TestStand Help for information about the following:

  • Suspend executions
  • Control how TestStand single-steps within executions
  • Set breakpoints
  • Stop executions prematurely

Terminate or Abort a Test

Refer to Terminating and Aborting Executions in the TestStand Help for information about creating stop requests to terminate an execution before the execution completes normally.