Use the System Source tab of the TestStand Deployment Utility to specify a workspace or directory that includes the components you want to deploy. The deployment utility analyzes the workspace file or directory by opening all the source files and searching for dependencies to generate a complete list of source files and dependencies to include in the deployment. For example, the deployment utility opens a workspace file and adds all the TestStand project files to the deployment, then opens each project and adds all the files in the projects to the deployment. The deployment utility continues this process until it identifies and adds all the dependencies of the test system.

Troubleshooting Deployment Analysis Errors

The deployment utility uses a log to report errors that might prevent test systems from functioning correctly, such as missing code modules. Resolve the errors and warnings on the development computer before you create or install a deployment because locating and resolving errors and warnings on the test station computer might require significant time and effort.

You can prevent many deployment issues by ensuring the test system is up-to-date and error-free by preparing the test system for deployment and by using the TestStand Sequence Analyzer to identify common problems with test sequences, such as steps that are missing code modules or code modules that TestStand cannot load.

If the deployment utility reports missing files, search the development computer to confirm the files exist in the correct directories. If the files exist on the computer but TestStand cannot find the files, use the Edit Search Directories dialog box to update the search directories, then exit and relaunch the deployment utility. NI recommends using paths relative to the workspace for TestStand projects and sequence files and paths relative to the calling sequence for all code modules to reduce the possibility of loading incorrect code modules.

If the deployment utility reports missing dependencies for code modules, you might not have installed the driver software the test system requires. Launch Measurement & Automation Explorer and expand My System»Software to review the NI software installed on the computer. Use the standard Microsoft Windows Control Panel facility for adding and removing programs to review the third-party drivers or other software installed on the computer.

In the following situations, the deployment utility reports that a sequence uses a file but the deployable image folder might not contain the file:

  • The sequence file dynamically references the file—You must manually add dynamically referenced files to the deployment.
  • The deployment utility filters files to prevent deployments from including operating system files—You can change the filtering settings using the Filter.ini file located in the <TestStand Application Data>\Cfg directory.