Configuring Sequence Editor and User Interface Startup Options

The TestStand Sequence Editor and all user interface applications support command-line options for opening and running sequences. You can append the startup options in the following table to the sequence editor and user interface command line. The "/" and "-" characters are valid command prefixes. Use spaces to separate command parameters. You must use quotation marks for arguments that contain spaces, such as "Test UUTs" and "C:\My Documents\MySeq.seq".

Option Purpose
sequencefile {sequencefile2}... Instructs the application to automatically load the sequence files at startup, as shown in the following example: SeqEdit.exe "c:\My Seqs\seq1.seq" "c:\My Seqs\seq2.seq"
/run sequencesequencefile Instructs the application to automatically load and run the sequence in the sequence file at startup, as shown in the following example: SeqEdit.exe /run MainSequence "c:\My Seqs\test.seq"
/runEntryPoint entrypointnamesequencefile

Instructs the application to automatically load and run the sequence file at startup using the Execution entry point you specify, as shown in the following example: SeqEdit.exe /runEntryPoint "Test UUTs" "c:\My Seqs\test.seq"

You must use the entry point name to specify the entry point to use, not the sequence name. The entry point name is displayed in the Execute menu in the sequence editor. To change the entry point name, edit the Entry Point Name Expression field, located in the Model tab of the Sequence options.
/editor Instructs the application to open in Editor Mode when the application supports editing, as shown in the following example: testexec.exe /editor
/goto location Instructs the application to display the item the location property object path specifies, as shown in the following example: testexec.exe c:\example.seq /goto "Seq[1].Main[4].TS.LoadOpt"
/operatorInterface Instructs the application to open in Operator Mode, as shown in the following example: testexec.exe /operatorInterface
/quit Instructs the application to exit after running the executions you specify, as shown in the following example: SeqEdit.exe /run MainSequence "c:\My Seqs\test.seq" /quitTestStand ignores the /quit option if the execution fails to launch.
/useExisting Instructs the application to use the existing running instance of the application instead of opening a new instance, as shown in the following example: SeqEdit.exe /useExistingTestStand ignores the /useExisting option when you specify the /quit option.
/setCurrentDir Instructs the application to set the current directory to the first directory in the File dialog box directory history list, as shown in the following example: SeqEdit.exe /setCurrentDirThe current directory is the directory the File dialog box initially displays when you open or save a file. Use this option to instruct the File dialog box to display the directory the File dialog box displayed the last time you ran the application. TestStand sets the current directory after processing the other command-line options.
/? Instructs the application to launch a help dialog box that contains a list of valid command-line arguments and then close immediately, as shown in the following example: SeqEdit.exe /?TestStand ignores all other options when you specify the "/?" option.
/outputToStdIO Instructs the application to write the status of completed executions as standard output, as shown in the following example: SeqEdit.exe /outputToStdIOWhen you run a user interface from the command line, the console window displays the standard output from the application.
/env <environment path> Launches the application in the environment defined in the .tsenv file located at <environment path>.
workspacefile Instructs the application to automatically load the workspace file at startup, as shown in the following example: SeqEdit.exe "c:\My Workspaces\ws1.tsw"This option applies only to the Sequence Editor.
sequenceanalyzerprojectfile Instructs the application to automatically load the sequence analyzer project file at startup, as shown in the following example: SeqEdit.exe "c:\My spaces\myAnalyzerFile.tsaproj"This option applies only to the Sequence Editor.

Refer to the ApplicationMgr.ProcessUserCommandLineArguments event for more information about processing user-defined command-line arguments in a user interface. When an error exists in the command-line argument, the Application Manager control generates an ApplicationMgr.ReportError event.