To launch the TestStand Sequence Editor or a TestStand User Interface in an environment,specify the /env command line switch followed by the path of the .tsenv file. For example:

SeqEdit.exe /env "MyEnvironment.tsenv"

If no environment is specified, the application runs without an environment, and the TestStand Engine uses the default locations for the various directories. Running without an environment is referred to as running in the “global” environment, though there is no global environment file.

For convenience, you can specify the global environment by explicitly passing an empty string for the environment file path on the command line. For example, both

SeqEdit.exe

and

SeqEdit.exe /env ""

launch the Sequence Editor in the global environment.

The following TestStand executables all support the /env command line switch to specify an environment:

  • TestStand Sequence Editor
  • TestStand User Interfaces
  • TestStand Offline Results Processing Utility
  • TestStand Sequence Analyzer Stand-Alone Application
  • TestStand File Diff and Merge Utility
  • Database Viewer Application

TestStand executables that launch other TestStand executables that use the TestStand Engine need to pass the current environment at launch, assuming they want the newly launched executable to use the same environment. For example, when you select the Tools»DatabaseViewer option in the Sequence Editor, the Sequence Editor uses Engine.GetEnvironmentPath with the /env switch to pass the current environment toDatabaseView.exe. To see this behavior, select Tools»Customize and examine the definition of Database Viewer command.

Note The Sequence Editor, full-featured TestStand user interfaces, Offline Results Processing Utility, Sequence Analyzer, and File Diff and Merge Utility all indicate the current environment in the status bar.