Debugging tests

If you encounter unexpected errors during running of your tests you can debug your scripts. To start debugging session select Run -> Run Tests menu. Project scripts will start running as usual however if any problems are encountered during running (such as checkpoint or action failure) the script will be suspended and the troubling line will be highlighted. Errors that cause break are the following:

• Failed verification
• Failed assertion
• Failed action on component (due to various reasons - for example if the component is not found or event name is incorrectly specified)
• Failed attempt to get a property of component
• Failed waitfor operator

Last message in message log will usually explain the problem (e.g. Expected vs Actual values will be shown for a failed checkpoint). You can switch to your application and inspect components and their properties. You can also examine your script and values of variables (if any are used) by placing mouse pointer over variable names.

When execution of the script is suspended due to an error you can still continue execution from the next command (except for failed assertion, which terminates the execution of current script).

When debugging you can execute test scripts step by step using Run -> Step command.