The Debug Mode GUI
Running a TestComposer script for debugging purposes is done in the Debug mode window, shown in Figure:Debug Mode Window
Figure:Debug Mode Window
To switch to the TestComposerDebug mode:
In the Script ribbon click the Debugbutton in the Test ribbon.
If the current script was not saved, on entering the Debug mode you are prompted to save it. Also, on switching to the Debug mode, the Test Steps table background changes to light grey, as a visual indication of the non-editing mode you are in.
While in Debug mode, runtime information on steps execution is displayed using highlighting based on the following colors:
: A currently executing step on the selected thread is highlighted green, with an adjacent arrow
icon.
: Currently executing steps that are paused because of encountered breakpoints, or because the Pause
button was clicked, are highlighted yellow.
: Active steps, such as a For or a RunProcedure step for example, whose execution has not completed yet because they are waiting for inner steps to finish, are highlighted using light green.
: Steps executing in parallel are highlighted in light purple. A step executing in parallel is said to spawn a thread.
: When a parallel step currently executing is selected in the Threads drop-down control, its entry point in the Test Steps table becomes highlighted purple.
IxLoad TestComposer │ User Guide |