Command Response
Some command steps, such as Execute and ReadFile, can have associated Response Templates that are used to parse the command's output and retrieve the values of user-defined tokens (`targets').
Retrieving portions of the command output is based on defining tokens (`targets') in the Response Templates associated with the step and then assigning Composer return variables to the command steps. In subsequent script steps, target values are then obtained by referencing the resulting composite variable and the target identifier.
For the currently selected step from the Script Steps table, the Command Response tab displays the command output and enables you to create a Response Template starting from the command response, or to assign an existing Response Template to the step.
If the script step was created using the GUI scripting support of the Edit mode and was never played, it has no command output and no associated Response Template. To such a script step you can either assign an existing Response Template resource, or, while still in Edit mode, play back the step in order to assign it a Response Template based on the actual command output called Local Step Response.
If a script step was added while directly interacting with a configured device using the Capture functionality available in the Edit mode, it has an associated Local Step Response template based on the command output.
For detailed information on defining a Response Template refer to Creating Response Templates .
When working with multiple scripts opened at the same time (MDI functionality), this tab displays information for the currently active test script.
IxLoad TestComposer │ User Guide |