<Behavior> Element - <Action> Element

<Behavior> Element

The ATML TD translator uses the <Action>/<Behavior> element to describe the tasks a test must perform to verify the state of the unit under test (UUT), including interacting with hardware and executing the test. TestStand sequence files handle the sequencing of all the tests required to verify the state of a UUT, and code modules perform each test.

The translator creates a LabVIEW or LabWindows/CVI code module to use with the step the translator creates for an <Action> element and copies information under the <AutomaticGeneration>, <Description>, <Extension>, <IeeeStd1641>, and <Operations> child elements of the <Behavior> element as XML comments in the code modules. Enable the LabVIEW or LabWindows/CVI option on the Code Module Settings tab of the ATML Test Description Translator Configuration dialog box to determine whether the translator creates code modules in LabVIEW or LabWindows/CVI, respectively.

• (LabVIEW) The translator creates a LabVIEW VI or updates an existing VI to use as a code module and creates or updates on the block diagram for the VI labels that correspond to the child elements of the <Behavior> element. The name of the VI is the same as the value of the name attribute of the parent <Action> element. The translator selects a connector pane pattern that best matches the number of controls and indicators.
• (LabWindows/CVI)  The translator creates a LabWindows/CVI project file and a source file or updates an existing project file and source file to use as a code module and inserts in the function definition of the source file comments that correspond to the child elements of the <Behavior> element. The name of the function is the same as the value of the name attribute of the parent <Action> element.

The translator encloses the XML comments that correspond to the child elements of the <Behavior> element within an <ATMLTranslatorComment> tag in the block diagram or function.

Completing the Partial Test Program  You must review the information in the XML comments, implement the operations and logic the comments describe, and assign the results of the operations to indicators in a VI or to [In/Out] parameters in a C file.

The code modules contain the code required to perform the tests the TD source file describes and verify the state of the UUT. When you run the complete test program, TestStand executes the associated code modules.

Incremental Update  The translator can incrementally update previously created code modules if you modify a <Behavior> element in the source TD instance document.

If the <Behavior>/<Operations> element contains only one <Operation> child element of the OperationMessageOut type, the translator creates a Message Popup step. The translator specifies that the message expression for the step is the value of the <MessageOut> child element of an <Operation> child element of the OperationMessageOut type.

Incremental Update  The translator uses the value of the ID attribute of the <Operation> element to identify the TestStand step to update. The translator does not define an incremental update behavior for the case in which two or more <Operation> elements exist with matching ID attribute values.

If the <Behavior> element contains a <TestGroupCall> child element, the translator creates a test step type that uses the Sequence Adapter.

Incremental Update  The translator creates a new test step that uses the Sequence Adapter if you change a child element of the <Behavior> element to a <TestGroupCall> element in the source TD instance document. The translator creates a new step and generates new code modules if a <Behavior>/<TestGroupCall> element changes to any other element.

See Also

ATML Test Description Translator Configuration dialog box

Message Popup Step

<Operation> Elements of the OperationMessageOut Type

Sequence Adapter

Test Step Types