Building a Package Distribution with the TestStand Deployment Utility

TestStand 2017 Help

Edition Date: November 2017

Part Number: 370052W-01

»View Product Info

Download Help (Windows Only)
NI TestStand 2014 Help
NI TestStand 2014 SP1 Help
TestStand 2016 Help
TestStand 2016 SP1 Help
TestStand 2017 Help

You can use the TestStand Deployment Utility to build a package-based distribution that contains the files the test system requires to execute successfully on a test station computer, such as sequence files, support files, user interface files, the TestStand Runtime, National Instruments run-time engines (RTEs), and National Instruments drivers and components. Additionally, the package distribution you build with the deployment utility can perform the following tasks:

  • Import hardware configuration information from Measurement & Automation Explorer (MAX)
  • Create program items, such as shortcuts
  • Launch a custom license agreement at install time

TestStand Deployment Utility can create the following types of package distributions:

  • Single Package— The test system files are packaged into a single .nipkg file. Dependencies you select are referenced by the package, and must be installed on the deployment target in order to install the package.
  • Repository— In addition to the main package, all dependent packages are also included in the deployment. A feed is generated which references all included packages. A feed is used to identify packages in National Instruments Package Management tools, such as NI Package Manager. To install the deployment, register the feed in NI Package Manager on the target machine.
  • Package Installer— In addition to the main package, all dependent packages are also included in the deployment. TestStand Deployment Utility also generates a standalone installer which installs all the packages on a machine. The installer will also install NI Package Manager if it is not present on the machine.

The Repository and Package installer modes also generate a Virtual Package (a package with no file contents) which depends on the main package, and all package dependencies. This package is generated for future support of creating supplemental packages to add to an existing package deployment.


WAS THIS ARTICLE HELPFUL?

Not Helpful