TestStand Deployment Utility

Publish Date: Feb 16, 2018 | 1 Ratings | 1.00 out of 5 | Print

Overview

This article describes the TestStand Deployment Utility and how it works.

Table of Contents

  1. What is TestStand Deployment Utility?
  2. How does the Deployment Utility work?
  3. Additional Information
  4. Additional Resources

1. What is TestStand Deployment Utility?

The TestStand Deployment Utility simplifies the complex process of deploying a TestStand system by automating many of the steps involved in deployment.

The Image folder created by the deployment utility contains an image of your system. This image can be copied over the network or put in an installer. Files located in this directory are modified copies of the original files used with the TestStand Sequence Editor.

 

Back to Top

2. How does the Deployment Utility work?

There are a couple of processes taking place in the Deployment Utility, listed below:

  • When deploying a workspace file, the Deployment Utility analyzes the workspace for any dependent files. For example, if your workspace contains a sequence file, the deployment utility searches the steps in every sequence of the file to find the referenced code modules.
  • The deployment utility also performs processing on sequence files in order to remove absolute paths.
  • ​The deployment utility corrects this potential problem (the absolute paths) by changing absolute path references in sequence files to relative paths that initiate from the search directories (Configure»Search Directories).
  • This analysis continues recursively until all files in the workspace hierarchy are analyzed.

 

Back to Top

3. Additional Information

  • Why can an Absolute path cause potential problems?

Absolute paths that are functional on your development computer may be invalid on the target computer, especially if the base installation directories are different.

For example, if you have installed TestStand to C:\TestStand on your development system and to C:\Program Files\National Instruments\TestStand on your target computer, the absolute path C:\TestStand\test.dll will be valid on your development computer but invalid on your target computer.

  • What are the many deployment steps automated by the TestStand Deployment Utility?

    Some of the deployment steps consist of collecting sequence files, code modules, and support files for your test system and then creating an installer for these files.

 

 

Back to Top

4. Additional Resources

Back to Top

Bookmark & Share


Ratings

Rate this document

Answered Your Question?
Yes No

Submit