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:

• Workspaces can contain files from multiple paths, which is more flexible than creating a deployment from a single root directory in the following ways:
  • You can map a directory in a workspace to a directory on the hard drive
  • You can add files from multiple directories to a single workspace directory
  • You can include only specific files from a directory on the hard drive in a workspace directory
• Workspaces contain references to files, not the files themselves. Therefore, deleting files from a workspace does not delete the files from disk.
• You can use projects as reusable, modular components that multiple workspaces can share. Defining projects by functionality can also help you easily add or remove features to or from a deployment by adding or removing the specific project to or from the workspace. For example, you can create a user interface project that includes all the files for the user interface you want to deploy.

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 create the deployment.

Creating a Workspace File for Deployment

Complete the following steps to create a workspace file.

1. Create a list of files to add to the workspace by identifying the components and required files for the test system.
2. Select File»New»Workspace File to create a workspace file. You must add one or more TestStand project files to the workspace.
3. Add individual files or all the files in a directory to the project file.

Avoid Inserting Code Modules in a Workspace You Use for Deployment

If you are using a workspace only to create a deployment, NI does not recommend inserting code modules that sequence files use in the workspace for the following reasons:

• Before creating a deployment, the deployment utility analyzes all the files in the workspace and includes the files that test sequences statically reference, including code modules.
• The list of code modules you insert in the workspace is a static list and does not automatically refresh when the sequence file changes. Therefore, you might deploy files that the test system no longer requires.