The TestStand Deployment Utility replaces absolute file path references with relative file path references because the location of files on a development computer might be different from the paths on the test station computer. For example, on the development computer, you might save files in the C:\Dev\TestSystem directory but install files on the test station computer in the C:\<Program Files>\TestSystem directory.

The deployment utility updates absolute path references in sequence files to use relative path references that initiate from one of the following search directories:

  • Current sequence file directory
  • <TestStand>
  • Windows\System32
  • Windows
  • <TestStand Public>

When the code module file you reference does not exist in one of these search directories, the deployment utility does not update the absolute paths. Therefore, the test sequence might not execute correctly on the test station computer.

The deployment utility also updates paths to code modules if you change the destination of code module files. For example, if a code module and its calling sequence file exist in the same source files directory but you change the destination directory for the code module to a subdirectory, the deployment utility updates the sequence file to use the new path to the code module when you create the deployment.

When you output VIs to packed project libraries, the deployment utility updates all appropriate steps in the sequence file to use the correct VI path and namespace.

Note The deployment utility does not modify custom step types. Instead, the deployment utility reports a warning on the Build Status tab when custom step types use absolute paths.