TestStand Directory Structure

TestStand 2019 Help

Edition Date: May 2019

Part Number: 370052AA-01

»View Product Info
Download Help (Windows Only)

To comply with Microsoft Windows restrictions on writing to the Program Files directory, TestStand 4.1 or later installs some files in different locations from previous versions of TestStand. Refer to the Directory Relocation section of the NI TestStand Version 4.2 Release Notes for more information about specific directories and files relocated in TestStand 4.1 or later.

TestStand 2014 or later installs files in the following default directories:

Directory 32-bit TestStand 64-bit TestStand
<TestStand> (32-bit Windows) C:\Program Files\National Instruments\TestStand <version>

(64-bit Windows) C:\Program Files (x86)\National Instruments\TestStand <version>
C:\Program Files\National Instruments\TestStand <version>
<TestStand Public> (Windows 10/8.1/7) C:\Users\Public\Documents\National Instruments\TestStand <version> (32-bit) C:\Users\Public\Documents\National Instruments\TestStand <version> (64-bit)
<TestStand Application Data> (Hidden by default) (Windows 10/8.1/7) C:\ProgramData\National Instruments\TestStand <version> (32-bit) C:\ProgramData\National Instruments\TestStand <version> (64-bit)
<TestStand Local Application Data> (Hidden by default) (Windows 10/8.1/7) <User Directory>\AppData\Local\National Instruments\TestStand <version> (32-bit) <User Directory>\AppData\Local\National Instruments\TestStand <version> (64-bit)

TestStand adds the TestStand, TestStandAppData, and TestStandPublic environment variables that reference the <TestStand>, <TestStand Public>, and <TestStand Application Data> directories respectively. You can use the environment variables in development environments to specify paths to files in these TestStand directories. For example, you can use these environment variables to build paths in the Additional Include Directories control in Visual Studio.

Refer to the Defining an Environment topic for more information about using environment variables in side-by-side TestStand environments.


Not Helpful