- Print
- DarkLight
The browser became unresponsive during test execution
In this article, you will learn the causes and fixes for the error message "The browser became unresponsive during the test execution. Please try to rerun the test or refer to the troubleshooting guide."
1. Webpage is loading slowly or loads a large amount of data
Test executions can be flaky when the webpage has performance issues or loads a large amount of data. If this is the case, please rerun the test.
2. An error occurs during or immediately after the "Go To" step
If this error occurs when executing a Go To step or immediately after, you may be able to fix the issue by adding a Sleep Step that waits 3-5 seconds.
3. Too many windows are left open
If you have opened many windows, add Close Window steps that close the windows you've finished testing.
How to add a "Close Window" step
"Close Window" steps cannot be added from the Scenario Details Page. It is automatically recorded when you close a tab or window (by clicking on x) while recording (Local Replay).
When a Close Window step is added, a step that switches to the test target window is added to the scenario immediately after the Close Window step (in the example below, "Switch To Initial Window").
4. Print dialog is displayed
Since print dialogs are displayed by the browser, if the print dialog is opened while the test is running, Autify cannot interact with the browser, resulting in this error.
If you need to test interactions with the Print dialog, please consider alternative methods such as manual testing.
Reference Article: Can I test actions against the print dialog?
If you are still having trouble...
Please contact our Customer Support team. We will help resolve the issue.