Executing a Script in Debug Mode

The Debug mode enables you to run the entire script in the TestComposer environment and debug the execution flow by visually following the steps execution and inspecting the displayed real-time commands and sessions output information.

While in Debug mode, breakpoints can be added to halt the script execution at a particular step. When a breakpoint is reached, or when a script is paused using the button, all active threads are stopped and the execution context enables you to visualize the call stack, the currently executing threads, or to retrieve the variables values at that moment.

Scripts cannot be edited while in Debug mode. If you wish to edit a script that is running in Debug mode, you have to switch to the Edit mode, perform the desired changes and then revert to the Debug mode.

The Debug mode GUI is also MDI enabled, meaning that switching between the Edit mode and the Debug mode while multiple tests are open in the TestComposer GUI preserves all open tests. However, since Debug mode execution is limited to executing a single test at once, you cannot run multiple tests in parallel. Thus, after having launched the execution of a script, you cannot execute any other script before the first script completes execution.

The Exclude/Include functionality described in Including and Excluding Steps from Execution, which enables the marking of script steps to be skipped at execution is also available in the Debug mode.