OVERVIEW CARD Architecture Overview Sequence File Execution Flow Execution Object Structure

NI TestStand
TM
TestStand Sequence Editor Sequence File Executions UUT Execution Object
TestStand development environment for creating, TestStand Custom You can execute a sequence directly or through a process model Device or component you are testing. Specifies how TestStand runs a sequence, its steps, and any Execution Object
modifying, executing, and debugging sequences. Sequence Editor User Interfaces Execution entry point, such as Test UUTs and Single Pass. Each subsequences it calls. You can suspend, interactively debug,
Thread Object 0 Thread Report

System and Architecture
Execution entry point is a sequence in the process model file that Offline Results resume, terminate, or abort executions.
Object n Object
Custom User Interfaces invokes a test sequence file. The TestStand Offline Results Processing Utility processes raw
Call Stack
Customizable applications that, depending on results files (.tsr) to generate reports or database tables at a Thread Object
mode, edit, execute, and debug test sequences on a Process User Interface Process Model Sequence File Execution time other than when sequence execution occurs or on a different Represents an independent path of control flow.
Root
test station. User interfaces are available in several When you start an execution through a process model Execution computer.
different programming languages and include Models Controls entry point, the process model defines how to test the UUTs. Report Object SequenceContext
full source code, so you can modify them to meet The Sequential model tests one UUT at a time. The Parallel model Report Generator Contains the report text. The process model updates the Object 0
specific needs. tests multiple independent test sockets at the same time. The Batch The report generator traverses test results to create reports in Report object, and the sequence editor displays it.
model tests a batch of UUTs using dependent test sockets. ATML, XML, HTML, and ASCII-text formats. You can fully SequenceContext
Process Models Application Programming Interface customize the reports. Call Stack Object n
Define standard operations for all test sequences, Process Model Plug-ins Lists the chain of active sequences waiting for nested
NI TestStand is flexible test management software that offers the following major features: such as identifying the unit under test (UUT), Process model plug-in sequence files use the results of each step to Schema Definitions subsequences to complete. The first item in the call stack is
Step Object 0
notifying the operator of pass/fail status, generating generate reports, log data to databases, or log data in a raw result Schema definitions define SQL statements, table definitions, and the most-nested sequence invocation.
• Out-of-the-box configuration and components • Example user interfaces with source code Sequence File
a test report, and logging results. TestStand TestStand Engine format for later processing. You can create custom plug-ins. TestStand expressions that define how to log results to a database.
that provide a ready-to-run, full-featured test for LabVIEW, LabWindowsTM/CVITM, includes three fully customizable process models: Executions You can fully customize the schemas. SequenceContext Object
Sequential, Parallel, and Batch. Test Socket Execution Represents the execution of a sequence that another Step Object n Current Step
management environment. Microsoft Visual Basic .NET, C#, and C++ For each test socket in the system, the Parallel and Batch process Database Logger sequence called. The root SequenceContext object is the
Microsoft Foundation Classes (MFC). User Interface Controls models launch a separate test socket execution that controls the The database logger traverses test results and exports data into least-nested sequence invocation.
• Numerous methods for modifying, configuring, Set of ActiveX controls and support APIs for testing of UUTs in the test socket. database tables using schema definitions.
Adapters Code Modules Current Step
and adding new components, which provide • An open language interface that provides support creating custom user interfaces.
Represents the executing step of the currently executing
extensibility so you can create a test executive for many application development environments TestStand Engine LabVIEW Adapter
.VI, .LVPROJ, .LVLIB,
.LVLIBP, .LVCLASS
Sequence File Executions sequence in the call stack.
that meets specific requirements without altering (ADEs). You can create code modules in a DLLs that provide an extensive ActiveX
the core TestStand Engine. You can upgrade to variety of ADEs and call pre-existing modules
Automation API for controlling and interacting
with TestStand. The sequence editor, TestStand LabWindows/CVI Adapter .DLL Sequence File Structure
newer versions of TestStand without losing the or executables. User Interface (UI) Controls, and user interfaces Process Model Sequence File Execution
use this API. C/C++ DLL Adapter .DLL
customizations. Sequence File Step Groups
• A comprehensive application programming Sequence File Executions
Sequential A sequence file contains any number of sequences, a set of TestStand executes the steps in the Setup step group first, the Main
.NET Adapter .DLL, .EXE Process Batch Process Model Parallel Process Model No Model
• Sophisticated sequencing, execution, and interface for building multi-threaded test systems Created by the TestStand Engine when you execute
Model
data types and step types the sequence file uses, and any global step group next, and the Cleanup step group last. By default, a
a test sequence using the sequence editor or variables that sequences in the sequence file share. sequence moves to the Cleanup step group when a step generates
debugging capabilities, and a powerful and other sophisticated test applications. ActiveX/COM Adapter .DLL, .EXE an error in the Setup or Main step group.
a user interface.
TestStand Sequence Editor that is separate from Sequences

the user interfaces. • Integration with third-party source code Adapters HTBasic Adapter .PRG Sequences contain groups of steps, local variables, and parameters Local Variables
used for passing data between steps and subsequences. Local variables store data relevant to the execution of the
control providers. Allow TestStand to call code modules in a variety
UUT Test Test Test Test Test Test
sequence. You can access local variables from within steps and
of different formats and languages. Adapters also Socket 0 Socket 1 Socket n Socket 0 Socket 1 Socket n
• User interface controls for creating custom allow TestStand to integrate with various ADEs to
Sequence Adapter .SEQ
Execution Execution Execution Execution Execution Execution
Types code modules defined in a sequence.
user interfaces and sequence editors. You can • Deployment tools to help you transfer a test streamline test code generation and debugging.
Sequence files contain definitions of all data types and step types
its sequences use. Variables and properties are instances of data Parameters
also create custom user interfaces in any system from development to production. UUT UUT UUT UUT UUT UUT UUT
types. Steps are instances of step types. For a step type, you can Use parameters to exchange data between calling and
Code Modules
programming language that can host ActiveX specify substeps that define standard actions, other than calling the called sequences.
Program modules, such as LabVIEW VIs (.vi) Built-In Step Types code module, TestStand performs for all instances of the step type.
or DLLs, that contain one or more functions to
controls or control ActiveX Automation servers. perform a specific test or action. TestStand adapters Call Executable UUT UUT UUT UUT UUT Steps
Pass/Fail Test Sequence File Globals Steps perform built-in operations or call code modules. A step is an
call code modules. Property Loader
Numeric Limit Test Sequence file global variables store data you want to access from instance of a step type, which defines a set of step properties and
Built-in Step Types
FTP Files any sequence or step within the sequence file in which you define default behaviors for each step.
Multiple Numeric Limit Test the sequence file global variable.
Define the standard behaviors for common testing Additional Results
String Value Test
Refer to the NI Trademarks and Logo Guidelines at ni.com/trademarks for information on National Instruments trademarks. Other product and company operations. Step types use adapters to call code Flow Control Steps
names mentioned herein are trademarks or trade names of their respective companies. For patents covering National Instruments products/technology, modules that return data to TestStand for further Results Results Results Results Results Results Results Results
Synchronization Steps Sequence File
refer to the appropriate location: Help»Patents in your software, the patents.txt file on your media, or the National Instruments Patent Notice at analysis, call executables, launch dialog boxes, Action
ni.com/patents. You can find information about end-user license agreements (EULAs) and third-party legal notices in the readme file for your NI product. implement test execution logic, or perform other Sequence Call Database Steps Types Sequences Sequence
Refer to the Export Compliance Information at ni.com/legal/export-compliance for the National Instruments global trade compliance policy and how operations. IVI Steps File Globals
to obtain relevant HTS codes, ECCNs, and other import/export data. Statement Process Model Plug-ins Data Type Step Type Step Groups—Setup, Local
User-Defined Step Types Label LabVIEW Utility Steps Parameters
Main, and Cleanup Variables
© 2003–2013 National Instruments. All rights reserved. Printed in Ireland. Define custom step properties and default behaviors Offline Results Report Generator Schema Definitions Database Logger ADO/ODBC
MessagePopup Properties
for each step of that custom type. You can also
Step
create custom data types.
User-Defined Step Types Substeps— Properties
Code Module
Templates
Create custom sequences, steps, and variables to Edit, Pre-Step,
use as templates to build sequence files. TSR ATML XML HTML ASCII- Microsoft SQL and Post-Step
Templates File Text Access Server
Oracle ...
373457E-01 Aug13
User Interface Overview TestStand Sequence Editor Overview Deployment Overview
TestStand includes separate user interface applications developed in LabVIEW, LabWindows/CVI, Visual Basic .NET, C#, and C++ MFC. Because You can use the fully customizable TestStand development environment to create, modify, execute, and debug sequences. You can also use the The sequence editor provides familiar LabVIEW, LabWindows/CVI, and Microsoft Visual Studio debugging tools, including breakpoints, single- Use the TestStand Deployment Utility to create a deployable image or a patch deployment of a TestStand system and an optional installer. The deployable
TestStand includes the source code for each user interface, you can fully customize the user interfaces. You can also create custom user interfaces using sequence editor to modify step types, data types, process models, and process model plug-ins. You can customize the environment by docking, stepping, stepping into or over function calls, tracing, a Variables pane, and a Watch View pane. In the sequence editor, you can start multiple concurrent image can contain sequence files, code modules, process models and supporting files, user interface applications, configuration files, and step types and
any programming language that can host ActiveX controls or control ActiveX servers. With the user interfaces in Editor Mode, you can modify sequences auto-hiding, and floating panes to optimize development tasks. executions, execute multiple instances of the same sequence, and execute different sequences at the same time. Separate Execution windows display each supporting files the TestStand system uses. The installer can contain all files from a deployable image or contain only a subset of files to create a patch
and create and modify sequence variables, sequence parameters, step properties, and so on. With the user interfaces in Operator Mode, you can start execution. In trace mode, the Execution window displays the steps in the currently executing sequence. When you suspend an execution, the Execution deployment for a previously deployed image.
multiple concurrent executions, set breakpoints, and single-step through sequences. window displays the next step to execute and provides single-stepping options.
Mode Distributed Files
Provides options Lists the files included in the
Step Types List Insertion Palette Sequences Pane Steps Pane Step Breakpoints Execution Pointer Windows for creating a full deployment and provides options for
Displays the TestStand Displays step types and Displays the sequences Displays the steps in the Performs built-in Suspends an execution Points to the currently Displays the sequence files, deployment or a configuring the installer destination
List Bar step types. templates you can insert in the sequence file. sequence you select on operations or calls before executing the step. executing step at the call executions, and other windows patch deployment location and settings for each file.
Lists the into sequence files. the Sequences pane. code modules. stack level you select. open in the sequence editor. and for specifying

TestStand Deployment Utility

currently related settings Installer Options
open for each type of Provides options for configuring
sequence deployment. installer settings for the deployment
files and and specifying which components
Insertion Palette to include from TestStand and other
executions. System Source
Displays step types National Instruments software, such
Provides options
and templates you as hardware drivers.
for specifying
can insert into
the workspace
sequence files. Build Status
file or directory
Sequence View

that specifies Displays progress and log

which files to information when analyzing files
deploy and the to include in a deployment and
location to create when building a deployment image
the deployment and installer.
image.

Sequence File Window

Lists steps in the Configure the settings for deploying a test system, including
sequence and

Execution Window
the components to install and the installer settings.
step group for the
sequence file you
select in the list bar. Documentation Overview
Execution View

The Guide to TestStand Documentation topic in the NI TestStand Help contains links to all the TestStand documentation in electronic format and
recommends the order in which you examine the documentation. You can access the Guide to TestStand Documentation topic in the following ways:
• Select Help»Guide to Documentation in the sequence editor.
• (Windows 8) Click the NI Launcher tile on the Start screen and select TestStand»Documentation»TestStand Guide to Documentation.
• (Windows 7 or earlier) Select Start»All Programs»National Instruments»TestStand»Documentation»TestStand Guide to Documentation.
Displays Templates List Step Settings Pane Analysis Results Pane Variables Pane Displays the threads, call Call Stack Pane Threads Pane Output Pane Watch View Pane NI TestStand Release Notes NI TestStand User Interface Controls Reference Poster
sequences and Organizes custom Specifies the settings for Displays the analysis results Displays globals, stack, and steps an execution Displays the Lists the threads in the Displays output Displays the values Use this document to learn about system requirements, installation Use this poster as a reference of the classes, properties, methods, and
other items in a sequences, steps, and the step, such as code for the current TestStand variables, parameters, runs. When execution nested sequence current execution. messages that of specified variables, instructions, information about new features, and other changes since the events found in the TestStand UI Controls API, as well as an illustration of
Displays the threads,
sequence file. variables you can use as module parameters, Sequence Analyzer project and properties, including completes, the Execution invocations for the expressions and code properties, and previous version of TestStand. the built-in connections between the TestStand UI Controls.
call stack, and steps
templates for building switching, flow control, and for each sequence file and the values, that steps can window displays the report thread you select. modules post to the expressions during
for the execution
sequence files. and post actions. workspace file you analyze. access at run time. for the execution. TestStand Engine. an execution. Getting Started with TestStand NI TestStand API Reference Poster
you select.
Use this manual to familiarize yourself with the TestStand environment Use this poster as a reference of the classes, properties, methods, and
and the basic features you use to build and run test sequences. events found in the TestStand API, as well as an illustration of API
inheritance.
NI TestStand Help
Workspace Pane Sequence Types User Manager
Report View

Use this help file to learn more about TestStand concepts, the TestStand Example Programs
Manages projects for source environment, the TestStand User Interface Controls and TestStand Engine Use the TestStand example programs, located in the <TestStand
code control (SCC) integration Hierarchy Window Window APIs, the TestStand ActiveX Automation server, the TestStand example Public>\Examples directory, to help you learn and understand key
Contains definitions Administers users for
and deployment. TestStand
integrates with third-party SCC
Window of custom data the test station, groups
programs, and deploying TestStand systems. concepts. Use these example programs as a starting point for applications
you create.
Displays a graph of types and step types to which users belong,
packages to add files, obtain NI TestStand VIs and Functions Help
the sequence call and all sequence files login names, passwords,
the latest versions of files, and Use this help file, accessible only from LabVIEW, to learn more about NI Developer Zone
callback relationships can use. and privileges.
check files in and out. Use TestStand-specific VIs and functions. Visit the NI Developer Zone at ni.com/zone for more advanced concept
among sequence files and
Displays the report TestStand project (.tpj) files and architecture information. For example, the NI TestStand Advanced
sequences to more easily
for the execution to organize sequence files and NI TestStand System and Architecture Overview Card Architecture Series provides more detailed information for experienced
visualize, navigate, and
you select. code module files in folders. Use this card to learn about the overall architecture of TestStand and as a TestStand users with complex projects.
maintain test sequences.
reference for key concepts.