NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

TestStand 2026 environment paths and SearchDirectories configuration

Solved!
Go to solution

We are migrating to TestStand 2026 Q3 Patch 1 and want to standardize the environment across several developer and test PCs.

Our shared SVN structure is:

 

We currently redirect:

However, in Configure Environment, the Global environment shows:

My questions are:

  1. Is SearchDirectories.ini loaded from the redirected CfgLocation, or from the default CommonAppData\Cfg directory?
  2. What is the precedence between CfgLocation, the TestStand Environment configuration, and the TestStandAppData environment variable?
  3. Is redirecting only the Cfg folder supported, or should the complete CommonAppData directory be remapped through a TestStand Environment file?
  4. Is sharing the configuration through SVN a recommended approach for keeping search directories, adapter settings, and other TestStand settings consistent?
  5. Are there configuration files that should remain machine-specific or user-specific?
  6. Apart from cleaning up search directories, mass-compiling LabVIEW code, and resaving sequence files in TestStand 2026, what should we check to reduce Sequence Editor startup time?

We want the development PCs to use the same controlled configuration without accidentally sharing local cache files, user-specific settings, or machine-specific paths.

0 Kudos
Message 1 of 3
(1,206 Views)
Solution
Accepted by topic author Viachi

@Viachi wrote:
[...]
  1. Is SearchDirectories.ini loaded from the redirected CfgLocation, or from the default CommonAppData\Cfg directory?local cache files, user-specific settings, or machine-specific paths.

SearchDirectories.cfg is loaded from CommonAppData\Cfg. Though I have seen inconsistencies when running a TestStand instance in Global Environment and my test one in parallel.

 


@Viachi wrote:
[...]
What is the precedence between CfgLocation, the TestStand Environment configuration, and the TestStandAppData environment variable?

 CfgLocation has precedence over TestStandAppData (we're talking about %TestStandAppData%, right?)


@Viachi wrote:
[...]
Is redirecting only the Cfg folder supported, or should the complete CommonAppData directory be remapped through a TestStand Environment file?

 


AFAIK you need to redirect the complete CommonAppData structure. I have asked Nigel to double check, here's the answer


CommonAppData is not limited to Cfg, but for an environment, Cfg is the key directory.

Path Purpose
CommonAppData\Cfg\ Shared engine configuration: StationOptions.ini, StationGlobals.ini, SearchDirectories.cfg, type-palette configuration, process-model plug-in settings, and related configuration files.
CommonAppData\ outside Cfg May contain application-created shared data, depending on installed components and enabled features. Do not assume a fixed complete file list across versions or installations.

For a custom environment, define CommonAppData and allow TestStand to create missing default configuration files on startup. Then copy only the configuration files you need from the source environment—such as SearchDirectories.cfg.

Exception: Users.ini remains global and is not isolated by CommonAppData; environments share the configured user database. The environment documentation describes this behavior and automatic creation of missing configuration files: 

 and 

 


@Viachi wrote:
[...]
Is sharing the configuration through SVN a recommended approach for keeping search directories, adapter settings, and other TestStand settings consistent?

I'd give this a yes

 


@Viachi wrote:

 [...]

Are there configuration files that should remain machine-specific or user-specific?

There may be use cases... yet the user centric stuff like editor settings go into LocalAppData AFAIK

 


@Viachi wrote:
[...]

Apart from cleaning up search directories, mass-compiling LabVIEW code, and resaving sequence files in TestStand 2026, what should we check to reduce Sequence Editor startup time


The measures you have described have an effect on the actual TestSequence load time rather than the SeqEdit launch time.

 

You might want to disable Nigel. You might also want to check with your IT for possible interference with ITSec software. And first of all, don't use old machines 😉

Message 2 of 3
(1,103 Views)

Thank you, this clarifies the distinction between redirecting CfgLocation directly and defining CommonAppData through a TestStand environment.

 

Our ProcMon capture confirms that the current registry CfgLocation override causes TestStand to read SearchDirectories.cfg from our SVN-controlled ProgramData\Cfg directory. However, for future TestStand versions we will move toward a version-controlled .tsenv file that defines the complete CommonAppData and Public roots, while leaving LocalAppData local to each user.

 

The global Users.ini exception is important for us because we are implementing separate SQL-based authorization through FrontEndCallbacks.

Our measurements also showed that the LabVIEW adapter selection has a significant effect on perceived startup: approximately 60 seconds with the LabVIEW Development System and 30 seconds with the corresponding Runtime Engine. Mass Compile and sequence conversion mainly affect module loading, but in our setup some LabVIEW and authorization modules are loaded from startup callbacks, so they can still influence the time until the editor is usable.

 

Message 3 of 3
(1,074 Views)