File Menu

The File menu in a TestStand User Interface contains the following options:
Note Menu items marked with an asterisk ( * ) appear only in Editor Mode.
  • Login —Launches the Login dialog box and prompts you for a login name and password. When you click Cancel , TestStand gives you no privileges. Use the Login command to log in as a different user. Each user can have different privilege settings , so logging in as a different user can change the privileges.
  • Logout —Logs out the current user.
  • New Sequence File* —Creates a new sequence file window.
  • Open Sequence File —Opens an existing sequence file. Use the Open File dialog box to select a file to load.
  • Close Sequence File/Close Execution —Closes the selected sequence file or execution.
  • Close All Sequence Files and Executions —Closes all open files and executions. For any execution that is currently running, the user interface prompts you to select whether to terminate, abort, or automatically close the execution when it completes.
  • Close Completed Executions —Closes all open executions that have completed.
  • Browse Workspace —Launches the Workspace Browser dialog box, in which you can load and unload workspaces, open sequence files that reside in a workspace, and perform source code control operations on files that reside in the workspace. You can open only one workspace file at a time. If a workspace file is already open, TestStand closes it before opening a new workspace.
  • Save* —Writes the contents of the active Sequence File window to disk.
  • Save As* —Writes the contents of the active Sequence File window to disk using a new name you enter.
  • Save All* —Saves all open files to disk, including sequence files, global variables, templates, and the workspace.
  • Unload All Modules —Removes from memory all step code modules , all code modules substeps call, and all sequence files not currently open in the list bar control. You can only use this command when there are no active executions. This command is useful when you want to rebuild a DLL after an execution but the DLL is loaded in TestStand. The application development environment you use to build the DLL cannot write out the new contents of the DLL until TestStand unloads it.
    Note
    • The .NET Adapter cannot unload .NET code module assemblies when Microsoft Visual Studio is debugging managed code in the TestStand process.
    • The ActiveX/COM Adapter cannot always unload DLL ActiveX Automation servers. When TestStand requests the operating system to unload the ActiveX server, the operating system ignores the request and keeps the ActiveX server in memory. You must exit the TestStand application to release the ActiveX DLL server.
  • Most Recently Used Files —Lists the most recently opened files.
  • Exit —Closes the user interface. Before exiting, the user interface closes all files and executions. For any execution that is currently running, the user interface prompts you to select whether to terminate, abort, or automatically close the execution when it completes. The user interface does not close until all executions are complete.

See Also

Open File dialog box

Workspace Browser dialog box