Run a Sequence File from Windows Explorer or Command Line

Issue Details

To run a sequence file, normally I have to start the TestStand Sequence Editor application, open the sequence file, then execute the entry point. I would like to simply double-click a sequence file in Windows Explorer to launch TestStand and execute an entry point automatically in one step.

Solution

The TestStand Sequence Editor and LabVIEW, LabWindows/CVI, Visual Basic, C# and C++ Operator Interfaces now support command line options to run sequences. Listed below are examples showing how to run a particular sequence in a sequence file, and how to run an execution entry point, such as Test UUTs. For the examples below we assume that you want to run the sequence file with one of the operator interfaces listed above. If you want to run the sequence file with the TestStand Sequence Editor replace "testexec.exe" with "SeqEdit.exe".

Run MainSequence in the ASequenceFileToRun sequence file:

testexec.exe -run MainSequence c:\sequenceFiles\ASequenceFileToRun.seq

Run the ASequenceFileToRun sequence file with the Test UUs execution entry point:

testexec.exe -runEntryPoint "Test UUTs" c:\sequenceFiles\ASequenceFileToRun.seq

Load multiple sequence files:

testexec.exe c:\sequencefiles\ASequenceFileToOpen.seq c:\sequencefiles\AnotherSequenceFileToOpen.seq

To make a sequence file execute TestUUTs simply by double-clicking it (e.g., from Windows Explorer), perform the following steps:

1. Create a shortcut for the sequence file; i.e., right-click on the sequence file and select Create Shortcut from the pop-up menu.
2. Right-click on the newly created shortcut and select Properties from the pop-up menu.
3. Select the Shortcut tab in the Properties window that appears.
4. In the Target field enter:

   testexec.exe -runEntryPoint "Test UUTs" c:\sequenceFiles\ASequenceFileToRun.seq

5. Click the Apply button and then click the OK button to close the Properties window.

 

Additional Information

For all the examples above, we assume that your operating system is configured to recognize relative paths to this executable. If you do not get good behavior from running testexec.exe from the command line, you may want to try an absolute path to your executable. Remember that if your paths have any spaces in them, you will be required to add "..." around your paths for the command line to interpret them correctly.