Home > Running a Script > Running a Script in Debug Mode

Running a Script in Debug Mode

Running a Script in Debug Mode lets you fix logical errors and check variables content.
 
WinTask debugger include all modern debugging features: breakpoints, tracing into routines or stepping over them, watch variables, ...

IMPORTANT - DEBUGGER LIMITS: As you step through the script code, the focus moves between the Editor window and the window of the application under automation. After executing each script line, WinTask debugger deactivates the application window and moves the focus to the Editor window. Before executing the next line, the debugger re-activates the application window. So for example, if the script right clicks a context menu, the activation of the Editor window will close the context menu and next step execution will fail. Step by Step Debugging should not be used within lines interfering with GUI.

The following articles provide more information on debugging in WinTask:
About Debug Mode
    Provides general information on how to use WinTask Debugger. 

Debug Mode in Action on a Sample Script
    An example that demonstrates the use of Debug Mode.

Step by Step Execution
    Describes how to trace step by step Script Execution.

Step Over
    Describes how to step over.

Step Out
    Describes how to step out.

Run to Cursor
    Describes how to stop the script on the current line.

Breakpoints
    Explains how you can create/use/remove breakpoints.

Watch Variables
    Describes the Watch Variables pane and how you can use it to watch values of variables.

Debug Toolbar
    Describes the available icons on the Debug Toolbar.