|Download Help (Windows Only)|
Use TestStand workspaces and projects to organize the files in a TestStand system. A workspace contains projects, and projects contain files or folders, which group files logically. For example, you can use a process model folder to contain process model sequences.
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. You can use the TestStand Deployment Utility to create a deployment that contains all the files you specify in a workspace file.
Using workspaces and projects as the source for deployments offers the following advantages:
Enable the From TestStand Workspace File option in the Deploy Files section on the System Source tab of the TestStand Deployment Utility and browse to or enter the path to the workspace file you want to use. When you add new files to the workspace, the deployment utility includes the new files the next time you build the deployment.
|Note When you use the deployment utility to deploy only the TestStand Engine or to deploy only the components in the <TestStand Public> subdirectories, you do not need to use a workspace file to organize the files for the deployment.|
Complete the following steps to create a workspace file.
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, for the following reasons, National Instruments does not recommend inserting code modules that sequence files use in the workspace if you are using the workspace only to create a deployment:
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.
Understanding Workspace Files section of Chapter 2, Loading and Running Sequences, of the Getting Started with TestStand manual