Debugging

This category enables you to customizes the following parameters affecting the Debug mode behavior.

  • Use debugger when playing steps in Edit mode (Summary view only): If selected, TestComposer autiomatically switches to Debug mode when steps are played while in the Edit mode (Summary view).
  • When selecting this option, you might also consider also selecting the Switch to Edit mode when execution completes in Debug mode option at the same time, in order to return to the Edit mode after execution completes.

  • Switch to Edit mode when execution completes in Debug mode: If selected, when running a script in Debug mode and the script execution terminates, the application automatically switches to the Edit mode.
  • Automatically start the test execution on entering Debug mode: If selected, upon entering the Debug mode, test execution is initiated.
  • Enable steps execution with user delay: This option determines the current playback mode selection of the Debug mode button.
  • Always show errors list on Execution Errors: When running a script, both in Edit and in Debug mode, and the Execution Errors tab is hidden, selecting this option determines the automatic displaying of the tab when encountering runtime errors.
  • Automatically switch to originating thread when breakpoint is reached: If selected, when a breakpoint is reached, the focus changes to the thread containing the step on which the breakpoint was defined.
  • Automatically play child steps in Edit mode: If selected, steps that are children of compound statements, such as For and While, are also executed when their parents are played.
  • Autoscroll test to track step being executed: If selected, the currently executing step is focused while running the script in debugging mode. As a result, when a script is executed, any executing steps that were initially shown collapsed in the Test Steps table is expanded and the executing step is always focused.
  • In the Debug window if you scroll manually to another step, while autoscroll option is enabled, the Autoscroll test to track step be ing executed check box is cleared and autoscrolling is disabled.

    Enabling autoscroll option can be useful, for example, when your test contains a RunProcedure step that calls a procedure with multiple steps, but the procedure body itself is located at a remote location in the test script.

  • Logs should contains Support Level Information: If selected, information is logged that can help support teams troubleshoot test configuration problems.
  • Global output debug information level, Session output debug information level: Enables you to select the debug information level for the Global Output tab as one of the following:
    • User trace commands: Only information for Trace commands is logged.
    • Step execution: A single line of execution information per step is logged.
    • Step response: Both step execution information and results are logged.
    • Troubleshoot: Detailed debug information is logged.
  • Session output debug information level, Session output debug information level: Enables you to select the debug information level for the Session Output tab as one of the following:
    • User trace commands: Only information for Trace commands is logged.
    • Step execution: A single line of execution information per step is logged.
    • Step response: Both step execution information and results are logged.
    • Troubleshoot: Detailed debug information is logged.
  • Log format: Enables you to specify the log format based on a number of predefined items (Time stamp, Session name, Message source, Message category, Security level, Text), or to define a custom format. In the latter case, select the Custom log format option and edit the format as desired in the field below.