Overriding PreBatch and PostBatch Model Callbacks
- Updated2026-07-27
- 1 minute(s) read
Purpose
This example demonstrates how to override the PreBatch callback to customize the batch and test socket serial number entry and how to override the PostBatch callback to customize the batch and test socket status report.
Example File Location
<TestStand Public>\Examples\Modifying Process Models\Overriding Model Callbacks - Batch Model\Overriding PreBatch and PostBatch Callbacks.seq
Highlighted Features
Batch process model
Major API
None
Prerequisites
None
How to Use This Example
This example overrides the PreBatch and PostBatch callbacks, but the OverrideSerialNumForBatchModel2.seq example sequence file overrides the PreUUT and PostUUT callbacks.
The advantages of overriding the PreBatch and PostBatch callbacks, and not the PreUUT and PostUUT callbacks, include the following:
- You can enable or disable test sockets.
- You can access data for test sockets you have disabled, terminated, or aborted.
The disadvantage is that you must set or retrieve information for each test socket in a loop instead of in parallel.
Related Information
- Model Callbacks in the Batch Process Model
- TestStand Directory Structure
- Batch Process Model
With the synchronization features of the Batch model, you can direct a step that applies to the batch as a whole to run only once per batch instead of once for each UUT. You can also specify whether certain steps or groups of steps cannot run on more than one UUT at a time or whether certain steps must run on all UUTs at the same time. The Batch model generates batch reports that summarize the test results for the UUTs in the batch.
- Overriding PreUUT and PostUUT Batch Model Callbacks