Using Breakpoints

Execution breakpoints represent user-defined locations where the script execution is halted, such as for example, for visualizing and inspecting execution environment information, such as TestComposer variables and executing threads.

Active breakpoints are symbolized by icons placed in the Breakpoints pane at the left of the Test Steps table.

For script executing parallel steps that spawn one thread for each running parallel step, upon reaching a breakpoint all threads are halted, not only the thread that has a breakpoint defined, and no other instruction is executed until the Play button is clicked.

To define breakpoints:

  1. While in Debug mode, hover the mouse button over the left Breakpoints pane, waiting for the cursor to change its shape to , then click once into the pane to add a breakpoint. The step is also selected as current step.
  2. Alternatively, you can define a breakpoint on the currently selected step by clicking the button, then clicking Enable breakpoint.

  3. Click again the breakpoint location to keep the breakpoint defined, but to toggle it off (inactive), such that it will not halt the script execution.
  4. Click the same location once again to completely remove the breakpoint.

Toggling a breakpoint on or off, as well as performing other breakpoint-related operations, can be also done from the Breakpoints tab, as described in Breakpoints.