Determining the Step Type to Create for an <Action> Element
- Updated2023-02-21
- 2 minute(s) read
The following table describes how the ATML TD translator determines which TestStand step type to create for each <Action> element based on its child element(s) <TestLimits>/<Limit>.
| Structure of Source TD Instance Document | Translator Behavior | Additional Action Required |
|---|---|---|
| The <Limit> element contains a <Mask> child element. | Creates a Pass/Fail Test step. | You must apply the specified mask and return the pass/fail status. |
| The value of the xsi:type attribute of the <Behavior>/<Operations>/<Operation> element is OperationCompare. | Creates a Pass/Fail Test step and adds the content of the <Limit> element as a comment to the code module that implements the parent <Action> element. | You must implement the limit comparison logic in the code module. |
| The <Action> element contains a customType attribute. | The customType attribute takes precedence over the limit processing. Therefore, the translator creates a step the customType attribute defines and adds comments for the <Limit> element to the code module. | You must implement the limit comparison logic in the code module. |
| The <Action> element includes a single numeric type <TestResult> element and the <TestResult>/<TestLimits> element contains only one numeric type <Limit> child element. | Creates a Numeric Limit Test step. | — |
| The <Action> element includes multiple numeric type <TestResult> elements and each <TestResult>/<TestLimits> element contains a numeric type <Limit> element. | Creates a Multiple Numeric Limit Test step. | — |
| The <Action> element includes a single <TestResult> element with multiple numeric type <Limit> elements. | Creates a Multiple Numeric Limit Test step. | — |
| The <Action> element contains a single string type <TestResult> element, the <TestResult> element contains a string type <Limit> element, and the <Limit> element contains an <Expected> child element with a comparator attribute that specifies a value of EQ. | Creates a String Value Test step. String Value Test steps support only EQ types of comparison, and the translator supports only case-sensitive comparison. | — |
| The <Action> element specifies an xsi:type attribute with a value of SessionAction. | Creates an Action step. | — |
For all other cases, the translator generates a Pass/Fail Test step and copies the XML content of the <TestLimits> element as a comment in the LabVIEW or LabWindows/CVI code module that implements the parent <Action> element.
 |
Completing the Partial Test Program You must implement in the code module the limit comparison that the <TestLimits>/<Limit> element describes, and return the comparison results to TestStand. Refer to the post-translation recommended actions section of the log file for more information about how you can implement the logic the <Limit> element describes. |
See Also
Creating LabVIEW Code Modules for <Behavior> Elements
Creating LabWindows/CVI Code Modules for <Behavior> Elements
Logging Translation Information