Create the Test XML Configuration File (.testdef)
- 更新时间2024-10-31
- 阅读时长1分钟
Create the Test XML Configuration File (.testdef)
To define the test parameters and endpoints being monitored during the test in TestStand and VeriStand, you will need to create a Test XML configuration file (.testdef). This configuration file allows the Battery Test System Web UI, the interface users interact with the Battery Test System through, to understand and run your test. This configuration file will need to contain a name and description for a test, as well as information on the properties of the test's parameters and aliases. The test XML configuration file can also contain information on test Battery Test System Web UI plugins if your system utilizes them. Refer to Test Package XML Conventions for XML file tag reference and a sample test XML configuration file.
相关内容
- 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.
- Test Package XML Conventions
The test XML configuration file (.testdef) defines the test parameters and endpoints being monitored during the test in TestStand and VeriStand. A pre-populated version of this XML file can be generated and edited for a defined test sequence from within TestStand by navigating to Tools Edit BTS Test Definition XML from Sequence . If a test definition file already exists for this test sequence, any changes detected based on new or deleted test parameters and endpoints will be merged into the existing file. Then you can use the test definition editor to further customize the configuration by defining how this test should appear in the BTS Web UI. For example, you could customize the display name that shows in the Web UI Test Definition selector menu, or the description that shows in the info tip in the Web UI; you could customize a string parameter type to expect a profile type file selection or define the minimum and maximum limits for a numeric parameter; or you could declare endpoints to be certain measurement types.