Debugging is a multi-step process that involves identifying a problem, isolating the source of the problem, and then either correcting the problem or determining a way to work around it. The final step of debugging is to test the correction or workaround and make sure it works.
LEAPWORK allows the user a very easy and convenient way to debug, allowing quickly investigating the issues that cause failure for their automation tests.
Users can do the debugging at two places in LEAPWORK Studio.
- At runtime environment within the flow section.
- In the Reporting tab by filtering out the required flow-based up different parameters like the run result, date/time, runtime, etc.
- The first step for debugging a flow is to identify the failure keyframe in the action/runtime logs. The failure reasons can be different in different situations depending on the flow requirements. Common errors comprise of timeout issues, an element not found, environmental or driver issues,etc.
- After getting the failure log, the user can just click on it to know which block is failing in the flow. For instance, in the above screenshot, it is the Start Web Browser which got failed due to insufficient timeout value which resulted in failure due to page latency issues.
- The final step is to land on to the flow, at the correct block, and rectifying the issue depending on the failure reason. In the above scenario, the simple fix is to increase the timeout on the Start Web Browser block.
For any clarification, please contact our Priority Support.