Executing Selected Steps
While in Edit mode, steps can be run directly from the Script Steps table with the step execution information displayed in the Execution Messages tab.
To run a script:
Multiple steps can be selected using the common Ctrl + Click for non-contiguous or Shift + Click for contiguous selection paradigm.
If breakpoints have been defined, these are not taken into account when playing back the selected steps.
While the step(s) is/are running, the Play
button appears grayed and cannot be accessed.
For executing steps, the command output is displayed as follows:
- For all steps, the error-, warning-, and information-level output is displayed in the Execution Messages tab. For some step commands that have multi-line output, only the first line is displayed. In such cases, you can select into the corresponding step's output in the Message column and click the
button, which renders the entire command output.
- For Execute type steps, the response from the configured device is displayed in the Command Response pane. If an Execute step had not been executed before and had no associated Response Template, a Local Step Response template based on the actual command output is assigned to the step.
- Steps that use device sessions for connecting to configured devices and execute commands on these devices display the actual device output in the Session Consoles window.
The procedure is executed using the default values for the procedure parameters. If any of the procedure parameters has no default value defined, a warning is displayed.
Although the Edit mode GUI supports the MDI functionality that enables you to have several tests open at the same time, execution of steps is limited to steps from a single test at once.
If at any point you want the Tcl interpreter to be reset, click the
button from the Test ribbon. Since by default the interpreter is not reset after executing steps in the Edit mode, resetting it could prove necessary after you have executed some steps that altered the initial variable values.
When running a step in the Edit mode, pay attention to execute all relevant associated steps in order to obtain meaningful results. For example, if you run a script step that uses a variable initialized in a previous step, you also have to run that step for the variable to be evaluated correctly.
IxLoad TestComposer │ User Guide |