Ce contenu n’est pas disponible dans votre langue préférée.

Le contenu est disponible dans une autre langue. Votre navigateur peut inclure des fonctionnalités qui vous aideront à traduire le texte.

Deploy Global Configuration Settings with TestStand Deployment Utility

Updated Mar 1, 2019

Reported In

Software

  • TestStand

Issue Details

I am creating a TestStand deployment using the TestStand Deployment Utility. I would like to include global settings such as Station Globals, Search Directories, and Tools Menu items in the deployment. How should I configure the TestStand Deployment Utility to achieve that?

Solution

Global settings like Station Globals, Search Directories, and Tools Menu configuration are stored in configuration files in the TestStand Cfg directory, which is located in <TestStand Application Data>\Cfg for TestStand 4.1 and later, or <TestStand>\Cfg for TestStand 4.0 and earlier. By default, the files in the TestStand Cfg directory are not included in the TestStand Deployment. You must include these files in your workspace for deployment unless you want to deploy the default settings.

To ensure that these configuration files are included in your deployment:
  1. Create a workspace file. The Using a TestStand Workspace File to Create a Deployment document walks through how to do this.
  2. Add the configuration files to your workspace.
  3. Select the configuration files in the Distributed Files tab of the TestStand Deployment Utility.


Note: the StationGlobals.ini and other config files located in the TestStand Cfg directory will not be automatically included by simply checking the Deploy Files in TestStand Public Directories option. Even if this option is checked, you must include the desired files in your workspace and deploy as normal.
 

Additional Information

TestStand 2016 and later supports deploying with environments through the TestStand Deployment Utility. TestExec.ini was also refactored into several smaller configuration files in TestStand 2016. For more information about the TestExec.ini refactoring, please see the Refactored TestExec.ini File page.

WAS THIS ARTICLE HELPFUL?

Not Helpful