Use the following controls to create user interfaces and test VIs to use with TestStand. Refer to the NI TestStand Help for more information about each control.

• TestStand UI Application Manager —The Application Manager control performs the following basic operations, which facilitate using the TestStand Engine in an application:
  • Processes command-line arguments.
  • Maintains an application configuration file.
  • Initializes and shuts down the TestStand Engine.
  • Logs users in and out.
  • Loads and unloads files.
  • Launches executions.
  • Tracks existing sequence files and executions.
  • Manages licensing.
  An application that uses the TestStand User Interface (UI) Controls must have a single Application Manager control that exists for the duration of the application.
• TestStand UI SequenceFileView Manager —A SequenceFileView Manager control performs the following tasks to manage how other visible TestStand UI Controls view and interact with a selected sequence file:
  • Designates a sequence file as the selected sequence file.
  • Tracks which sequence, step groups, and steps are selected in the selected sequence file and tracks the expansion of the step groups.
  • Displays aspects of the selected file in the visible TestStand UI Controls to which it connects.
  • Enables visible TestStand UI Controls to which it connects to change the selected file, sequence, step group, and steps.
  • Provides methods for executing the selected sequence file.
  An application must have one SequenceFileView Manager control for each location, such as a window, form, or panel, in which you display a sequence file or let the user select a current sequence file.
• TestStand UI ExecutionView Manager —An ExecutionView Manager control performs the following tasks to manage how other visible TestStand UI Controls view and interact with a selected TestStand execution:
  • Designates an execution as the selected execution.
  • Tracks which thread, stack frame, sequence, step group, and steps are selected in the selected execution.
  • Displays aspects of the selected execution in the visible TestStand UI Controls to which the control connects.
  • Enables visible TestStand UI Controls to which the control connects to change the selected thread, stack frame, sequence, step group, and steps.
  • Generates events to notify the application of the progress and state of the selected execution.
  • Provides debugging commands
  • Updates the ReportView control to show the current report for the selected execution.
  An application must have one ExecutionView Manager control for each location, such as a window, form, or panel, in which you display an execution or let the user select a current execution.
• TestStand UI Button —Connect a manager control to a Button control to specify that the button performs a common user interface command, such as Open Sequence File . The Button control uses a localized caption and automatically enables or disables depending on the application state.
• TestStand UI CheckBox —Connect a manager control to a CheckBox control so users can toggle the state of a common user interface command, such as Break on Step Failure When you connect to a command, the CheckBox control automatically updates the caption text, visibility, and enabled state. When you enable the checkbox, the checkbox executes the command, which toggles the state of the command.
• TestStand UI ComboBox —Connect a SequenceFileView Manager or ExecutionView Manager control to a ComboBox control so users can view or select from a list of sequence files, sequences, step groups, steps, executions, threads, or stack frames. Connect an Application Manager control to a ComboBox control so users can view or select the default adapter of the TestStand Engine.
• TestStand UI Label —Connect a manager control to a Label control to display text information about the application state in the label, such as the name of the current user or the status of the current unit under test.
• TestStand UI ListBar —Use a ListBar control to display multiple pages, where each page contains a list of items users can view or select. Connect a SequenceFileView Manager or ExecutionView Manager control to a ListBar page so users can view and select from a list, such as the active sequence file or execution. Connect an Application Manager control to a ListBar page so users can view or select the default adapter of the TestStand Engine.
• TestStand UI VariablesView —Connect a SequenceFileView Manager or an ExecutionView Manager control to a VariablesView control to display the variables and properties in the selected file or execution. You can modify values of existing properties and variables, and you can insert and delete variables when editing a sequence file.
• TestStand UI ExpressionEdit —Use an ExpressionEdit control so users can edit a TestStand expression with syntax coloring, context help, and statement completion. Although you typically do not need to edit expressions in a user interface application, you can connect a manager control to a read-only ExpressionEdit control to display text information about the application state, such as the pathname of the sequence file selection or the name of the current user. You can also use ExpressionEdit controls in dialog boxes for step types and in tools in which you prompt users to enter a TestStand expression.
• TestStand UI ListBox —Connect a SequenceFileView Manager or ExecutionView Manager control to a ListBox control so users can view or select from a list of sequence files, sequences, step groups, steps, executions, threads, or stack frames. Connect an Application Manager control to a ListBox control so users can view or select the default adapter of the TestStand Engine. Use a ListBox control to display multiple pages, where each page contains a list of items that users can view or select.
• TestStand UI ReportView —Connect an ExecutionView Manager control to a ReportView control to display the report for the selected execution.
• TestStand UI SequenceView —Connect a SequenceFileView Manager control or an ExecutionView Manager control to a SequenceView control to display the steps of a sequence from a selected file or execution. The SequenceView control displays the steps in a list with columns you specify when you configure the control. The SequenceView control maintains a cursor that indicates the last active item you clicked using the mouse or highlighted using the arrow keys. The control denotes the cursor using a dotted box that outlines the step. Use the SequenceView control to select one or more steps at a time. Use the SequenceFileView Manager control connected to the SequenceView control to control which sequence, step groups, and steps are selected in the file and to track the expansion of the step groups.
• TestStand UI StatusBar —Connect a manager control to panes of a StatusBar control to display text, image, or progress information about the application state. You can programmatically control individual StatusBar panes to display custom information. You can connect the panes to CaptionSources, NumericSources, and ImageSources on the Application Manager, ExecutionView Manager, and SequenceFileView Manager controls.
• TestStand UI InsertionPalette —Connect a SequenceFileView Manager control to an InsertionPalette control so users can insert steps and template items into a sequence file by dragging or double-clicking.
• Legacy —Use the controls on the Legacy palette for previous versions of TestStand and the LabVIEW Test Executive Toolkit.
  Note TestStand 2012 or later no longer includes support for converting a LabVIEW Test Executive Toolkit sequence file to a TestStand sequence file. Visit ni.com/info and enter the Info Code exgin9 for more information about converting a LabVIEW Test Executive Toolkit sequence file to a TestStand sequence file .
  • Input Buffer —Use only for compatibility with the LabVIEW Test Executive Toolkit as a string control to pass parameters to VIs.
  • Invocation Info —Use only for compatibility with the LabVIEW Test Executive Toolkit as a cluster that contains information about the execution state. If you are creating new tests, use the sequence context instead.
  • Sequence Context —A sequence context is an object in the TestStand API that represents the execution state of a sequence. For each active sequence, TestStand maintains a sequence context you can use to access all the objects, variables, and properties that relate to the execution of the sequence.
  • Test Data —Specifies the standard data the TestStand LabVIEW Adapter requires for legacy test VIs.