Errors loading pages in Chrome
I've been running into a lot of intermittent failures when loading pages in Chrome. The Page.ToUrl and Page.Wait methods appear to return almost immediately, especially when reloading a URL that is a...
Forum Discussion
Hi, Tanya,
Our test platform was running TestExecute 9.30, so I have updated it to 9.31. This solved the issues with Page.ToUrl, so that's good.
This leaves my problem of waiting for a page to load after clicking a script-based link. Example: There is a "Log out" link on application pages that ends the user's session and redirects them to the home page. If I click the link and immediately call Page.Wait, the method sometimes returns immediately, before the page redirect. My object searches then find the objects on the old page and the test fails.
I've tried several different methods of determining when the page has started loading before calling Page.Wait, and they have all failed in Chrome 30. They all work in IE10 and Firefox 24.
- Loop to check that Page.contentDocument.readyState is anything but "complete".
Failed with "object does not exist" or "object does not support property" because the contentDocument was being destroyed between the moment I checked whether it was valid and the moment I actually tried to check the readyState.
- Loop to check whether Page.contentDocument is Nothing.
Failed with random "Unspecified error" script exceptions. When I added native error handling to catch these exceptions, I had a random error occur that the Page object did not exist.
Next step is to reorganize the loop to obtain a new Page object every time...
Our test platform was running TestExecute 9.30, so I have updated it to 9.31. This solved the issues with Page.ToUrl, so that's good.
This leaves my problem of waiting for a page to load after clicking a script-based link. Example: There is a "Log out" link on application pages that ends the user's session and redirects them to the home page. If I click the link and immediately call Page.Wait, the method sometimes returns immediately, before the page redirect. My object searches then find the objects on the old page and the test fails.
I've tried several different methods of determining when the page has started loading before calling Page.Wait, and they have all failed in Chrome 30. They all work in IE10 and Firefox 24.
- Loop to check that Page.contentDocument.readyState is anything but "complete".
Failed with "object does not exist" or "object does not support property" because the contentDocument was being destroyed between the moment I checked whether it was valid and the moment I actually tried to check the readyState.
- Loop to check whether Page.contentDocument is Nothing.
Failed with random "Unspecified error" script exceptions. When I added native error handling to catch these exceptions, I had a random error occur that the Page object did not exist.
Next step is to reorganize the loop to obtain a new Page object every time...