A test executive organizes and executes sequences of reusable code modules you can create in a variety of programming environments.

The following concepts are applicable to test executives in general:

• Code module—A program module, such as a Microsoft Windows DLL or LabVIEW VI (.vi), that contains one or more functions that perform a specific test or other action.
• Step—An individual element of a test sequence that can call code modules or perform other operations.
• Sequence—A series of steps you specify to execute in a particular order. Whether and when a step executes depends on the results of previous steps.
• Subsequence—A sequence another sequence calls as a step.
• Sequence file—A file that contains the definition of one or more sequences.
• Sequence editor—A program that provides a graphical user interface (GUI) for creating, editing, executing, and debugging sequences.
• User interface—A program that provides a GUI for executing sequences on a production station. A sequence editor and user interface can be separate applications or different aspects of the same application.
• Test executive engine—A module or set of modules that provide an API for creating, editing, executing, and debugging sequences. A sequence editor or user interface uses the services of a test executive engine.
• Application Development Environment (ADE)—A programming environment, such as LabVIEW, LabWindows™/CVI™, or Microsoft Visual Studio, in which you create code modules and user interfaces.
• Unit Under Test (UUT)—The device or component to test.
• Deployment—An image or an installer for an image to transfer a test system from development to production.