Item Names

For a code module, the item name is a description of the module call. For UUTs, Batches, and Lots the item name includes the serial number or lot id, if specified. If it is needed to distinguish separate items, the item name includes an index value. For Steps, the item name is the name of the step. If multiple steps have the same name, the item name includes the unique identifier for the step.

If item names coincide for different types of operations, the profiler appends the type of operation to the item name, such as 'Lock' or 'Step'.

Locks and Other Synchronization Item Names

You typically name TestStand locks after the resources the locks protect, such as DMM1 or DC Power Supply. The profiler displays the name of the lock, or other synchronization object, as the profiler item name. Thus, if you follow the convention of naming your locks after the resources they protect, you can easily use the profiler to observe the usage of and contention for your physical and logical resources.

If you create a lock or another type of synchronization object with an empty name, TestStand names the object for you, such as Unnamed Synchronization Object N. TestStand also automatically selects an item name in the following cases:

  • When you use the Use Lock to Allow Only One Thread at a Time to Execute the Step option on the Synchronization panel of the Properties tab of the Step Settings pane and not specifying an existing lock
  • When you use the Batch Synchronization option on the Synchronization panel of the Properties tab of the Step Settings pane
  • When you use a Wait step
  • When you use a Use Auto Scheduled Resource step

In these cases, TestStand creates an item name by combining the unique ID of the step with the run-time ID of the file that contains the step. However, for readability, the profiler window shows the name of the step as the item name. If the step name is not a unique item name, the profiler appends the unique id for the step to the step name. For Use Auto Scheduled Resource steps that do not have unique names, the profiler first attempts to make the step name unique by appending a description of the locks the step acquires.