|NI TestStand 2014 Help|
|NI TestStand 2014 SP1 Help|
|TestStand 2016 Help|
|TestStand 2016 SP1 Help|
|TestStand 2017 Help|
Create a workspace to organize and access development files. Use workspaces early in development so you can easily keep track of files while you are developing. A workspace file (.tsw) contains references to any number of TestStand project files. A project file (.tpj) contains references to any number of other files of any type.
Use project files to organize related files and directories of files in the test system. You can insert any number of files into a project. For example, you can use a project file to organize a sequence file, code module source files, and other supporting files.
When you use a workspace, you must define at least one project. However, defining multiple projects in a workspace can help you better organize a test system. For example, you can define product model projects that contain all the tests required for the specific product model. When a model becomes obsolete, you can remove only the corresponding project from the workspace to update the test system.
Use workspace files to help organize and access development files, to perform source code control (SCC) operations in the TestStand Sequence Editor or in a TestStand User Interface, and to store debugging information, such as breakpoints and watch expressions.
In the TestStand Sequence Editor, use the Workspace pane to view and edit a workspace file and the project files it references. You can open only one workspace file at a time. To open an existing workspace file, select File»Open File. To create a new workspace file, select File»New»Workspace File.
Use workspace files early in development to easily access files in a source code control (SCC) system. When TestStand loads a workspace, the properties of a workspace specify whether TestStand attempts to connect to an SCC provider. When TestStand successfully connects to an SCC provider, you can use the commands in the Workspace context menu and the Source Control menu to check out and check in files from SCC. If an SCC provider returns warning or error messages when performing SCC operations, the sequence editor displays the messages in the Output pane.
To perform SCC operations on files from within TestStand, select an SCC provider on the Source Control tab of the Station Options dialog box and configure the SCC settings for the workspace on the Source Control tab of the Workspace Object Properties dialog box.
|Note TestStand integrates with any 32-bit SCC provider that supports the Microsoft Source Code Control Interface. 64-bit TestStand supports 32-bit SCC providers only and does not support 64-bit SCC providers.|
You can right-click a sequence file in the workspace and select Insert Code Modules from the context menu to automatically include the code modules a sequence file uses. However, if you are using a workspace only to create a deployment, National Instruments does not recommend this technique.
|Note TestStand does not dynamically update code modules. If you add or remove any code modules from your sequence files, you must delete the CodeModules folder and then select Insert Code Modules again from the Workspace Browser context menu to add the code module files back to the workspace.|
When a sequence file in a workspace changes or if you are using a workspace to interface with an SCC system, complete the following steps to manually refresh the code modules directory to avoid deploying files that the test system no longer requires.
You can use a workspace and project files to specify all the required files the TestStand Deployment Utility collects to successfully distribute a test system to a target computer. The deployment utility creates an image or an installer for the test system.