Because ATML uses the XML standard for describing ATE and test data, it takes advantage of recursion and extensibility, key technical benefits that give test systems greater flexibility in defining interfaces.
The ATML standard also includes general-purpose elements, such as OtherData and Extension, which can store additional information not specifically out-lined in the ATML schema.
To further gain insight into an ATML component, here is a look at the ATML TestResults component, which describes how test results should be organized.
As ATML defines, a test is any procedure for evaluating or quantifying the operation of a device or system.
The main result-collecting element for each ATML TestResults schema is the ResultSet element, which requires the ID attribute to properly identify the element.
There are three steps to ATML reporting behind the scenes of a NI TestStand sequence execution.
To further illustrate the TestResults schema, the ATML TestResults report in Figure 1 is generated from the TestStand example test sequence in Figure 2.
Upon executing the example test sequence, TestStand automatically collects each test-step result and generates an ATML TestResults-compliant test report that it stores as an * .
In addition to the TestResults component which defines the result reporting system interface, eight other components comprise the ATML standard.
The ATML Common schema defines common types and attribute groups among the other eight schemas or their subschemas.
The ATML TestDescription schema outlines all the common interfaces for describing and executing a test program on a particular UUT.
The ATML Instrument schema shares information describing an instrument interface definition within the tester and primarily is charged with commonly defining the instrument capabilities to facilitate instrument selection and validation during tester/test verification.