@Russ_Thomas
Yes, I am because when the new window opens, my test is doing WebUI.verifyelementvisible() on one of the objects on new tab.
When I switch to the new handle, the new page keeps loading forever, but as soon as I click on ‘X’ icon on my browser manually, the test finds the object instantly and passes.
Just to add to this, when I follow this scenario on regular chrome browser (the one that is not being controlled by automated test software) the new page loads successfully instantly. But for some reason, when the same scenario is executed on the browser instance initiated by Katalon, the page keeps loading forever.
And after 300 seconds, the test stops, fail and throw timeout error. At that same instance, the page stops loading.
Which is the correct behavior because the test has failed – no human would wait 300 seconds, so timing out at that point and failing the test is reasonable behavior.
Here’s my diagnosis…
The page is waiting for something to arrive from the server. It never arrives.
You should try to find out what is hung up using the network tab in DevTools. Then, submit a report to the developers and explain their server is not responding in a timely manner.
Clicking the stop-loading button is not a valid means of completing a test case. Web pages should load in a timely manner and allow the test case to complete normally.