Structure and Naming of Battery Test Package Folders

Battery test packages must be constructed and named according to a specific file hierarchy so that the Battery Test System can utilize them correctly once they have been loaded into long-term storage by the Battery Test Package Loader.

Battery test packages must be laid out using the hierarchy in the following figure, with each folder in the top-level battery test package folder representing a package type.

Figure 1. Battery Test Package Top-Level Folder Hierarchy


You can choose certain folder names, while you must use predefined names for others.

  • Discretionary naming: You can choose the name for the top-level folder, represented with BTSPackages in this example.
  • Obligatory naming: Within that top-level folder, you must use the folder names ConnectorInterfaces, DUTs, Tests, and TestStations.

These package folders should contain top-level folders for individual packages, as well as a shared folder for resources and files that are shared across packages of the same type, such as sub-sequences that are shared by one or more test packages. You should store all files associated with a package in the package's folder and the package type's shared folder.

For example, the Tests package top-level folder should contain folders and files associated with each specific test, as well as a Shared folder that can store files that can be used by one or more tests. Each test's folder could contain the main test sequence, folders that organize the TestStand and real-time sequences associated with that specific test, and a folder that stores the test's profiles, as depicted in the following figure.

Figure 1. Test Battery Test Package Folder Hierarchy Example


When you submit a test package, the Battery Test Package Loader gathers all of the relevant files, preserving their relative paths, and stores them in the long-term storage system you have defined.

When a test plan is run from the BTS Web UI, the files associated with that test plan are pulled from long-term storage and deployed to the Lab PC with a layout as depicted in the following figure.

Figure 1. Examples: Package File Set (the Left Side of the Following Image) and Deployed Test Plan Package with DUT 1, Test 1, and Test Station 1 (The Right Side of the Following Image)


Note It is strongly recommended to use version control, such as a Git repository, when creating and editing your battery test packages' files using the hierarchy shown in this section. This provides for traceability of your files and streamlines file sharing between the Engineering PCs and the BTS Server without compromising the file hierarchy the Battery Test Package Loader needs to load packages into long-term storage.
Note Although the name of a test folder and its contents can be defined however you like, it is recommended that the main sequence file be placed at the top level of each Test folder.