Troubleshooting element identification during test execution

Availability: Version 3.1

Debug Mode

accelQ  supports Debug mode when you run a test. This enables an interactive troubleshooting tool during the test execution. Element identification is one of the significant contributors to test automation brittleness.

If an element is not detected for whatever reason, test execution is automatically paused (when running in Debug mode), allowing you to interact with the application to analyze the discrepancy. Test report includes a summary of the analysis allowing you to reconcile. 

• Helps with troubleshooting element identification issues as the test execution is happening. Lot of times, it may be difficult to reproduce issues with dynamic elements after the conclusion of the test. 
• In addition to addressing element identification failures in real time, this powerful feature also helps greatly as a learning aid in setting up suitable element identification in the first place.
• Works across all the supported execution browsers (Firefox, Chrome, Safari and IE), so it is easy to find issues specific to a browser type.
• Interactive and real-time feedback makes it easy to determine optimal selector criterion.

Enabling Debug Mode

During test execution, turn-on the Debug flag in the Run modal. This will automatically pause test execution when the test is unable to find an element.

Note: When scheduling a future execution or a CI job, you cannot enable this flag.

Troubleshooting element ID

If the system detects any element identification failure, a popover window opens on the test browser and allows dynamic and interactive analysis of the issue. You can compare the properties for the saved element with that of the element displayed on the screen. You can also make changes to the saved element properties, including regular expression patterns. As you make changes, debugger provides real time feedback on the screen matches.

Once you are in the Debug session, you also have an ability to abort the test if desired.

Test Report

When the debug session is active during test execution, a message is displayed in the test report indicating the test is paused. This gets timed out in 120 seconds, if you do not start interaction within that time.

Test report also summarizes the analysis and findings during the troubleshooting session.