A sequence file (.seq) contains any number of sequences, a set of types the sequence file uses, and any global variables steps and sequences in the file share.

TestStand includes the following types of sequence files:

  • Normal sequence files—Most sequence files you create are normal sequence files that include sequences to test UUTs.
  • Process model sequence files—Normal sequence files specify that they always use the station process model, a specific process model, or no process model.
  • Callback sequence files—TestStand uses callback sequences under specific circumstances. Sequence files can contain sequences that override these callbacks. Usually, an application has one Station callback sequence file and one Front-End callback sequence file.

From within the TestStand Sequence Editor, use the Sequence File Properties dialog box to specify the type of sequence, the sequence file process model settings, and other sequence file properties.

Sequence files contain the type definitions for every step, property, and variable the sequence file contains. Use the Types pane to view and edit the types a sequence file contains.

Viewing the Hierarchy of Sequence Calls

Use the Sequence Hierarchy window in the TestStand Sequence Editor to display a graph of the sequence call and callback sequence relationships among sequence files and sequences to more easily visualize, navigate, and maintain test sequences.

Comparing and Merging Sequence Files

The TestStand File Diff and Merge utility is a stand-alone application you can use to compare and merge non-type differences between two or three sequence files and compare type differences among two sequence files or type palette files.

Password-Protecting Sequence Files

TestStand supports password-protecting sequence files to discourage editing and viewing within the TestStand Sequence Editor and TestStand User Interfaces that use the TestStand User Interface (UI) Controls. The TestStand API limits access to a file protected from viewing but cannot prevent access to the file content during execution. NI does not recommend using passwords as the only way of protecting intellectual property.

Analyzing Sequence Files

Use the TestStand Sequence Analyzer in the TestStand Sequence Editor or the stand-alone sequence analyzer application to analyze projects outside of the TestStand Sequence Editor.