Debugging with TestArchitect
The TestArchitect debugger allows you to run an application under test interactively while observing the action lines and results at each stage of execution, as well as the state of the AUT. Variables, arguments, and settings at each stage may also be observed, and modified.
Since tests do not always execute as expected, TestArchitect offers test-level debugging. Debugging allows you to pause the execution at any point. Once the test is stopped, you can look at the state of the running application under test, inspect the values of variables, arguments, and settings at the point of the pause.
There are two means by which a test may be paused for debugging:
- Prior to executing a test, you may set one or more breakpoints in the test module or its action definition(s). Then execute the test in Debug mode.
- Upon encountering an automation problem (warning or error) during execution, TestArchitect automatically pauses, offering you the option of entering Debug mode at the point of the problem action line.
- Running a harness in debug mode along with multiple harnesses using batch file(s) is allowable.
- Technically, you can run a harness in ordinary mode from TestArchitect Client first and then run another harness in debug mode. It is highly inadvisable to try this because it can cause unexpected functions.
- It is impossible to run a harness in debug mode first and then run more harness(es) in debug/ordinary/compilation mode.
With execution halted, the debugger toolbar offers various functional buttons to help you debug the action lines.
A breakpoint is a location in your action lines that has been designated as a point at which execution is to be paused. With execution thus halted, you can view information about the running application’s state at the given point.
Starting the debugger
After defining breakpoints, you can run your test procedure through the debugger.
If you no longer need a breakpoint, delete it.
Sometimes you may want to disable a breakpoint without doing away with it entirely. Execution is not paused when it meets a disabled breakpoint. The breakpoint remains marked in the margin for your reference, and can be re-enabled when again needed.
Reactivating a disabled breakpoint.
Debugging in a remote desktop session
How to debug a harness in a remote desktop session.