jonathan_ehman
11 years agoNew Contributor
Troubles with Firefox reliability during TestComplete test
Our company runs a large number of tests on our email client using TestComplete. This includes going to each page and making sure that it loads and certain information is displayed in multiple languages.
We found that of all the browsers, Firefox was the fastest and most reliable with TestComplete. However, there are times that FF will simply stop loading a page with no warning. Going to the page and testing in the same conditions reveals no issues with the page itself.
The following are some of the things we did to increase reliability.
We currently completely shutdown (as in end the process of) Firefox after each test using the Sys.Process("firefox").Close(). When the Firefox process fails to close, then we call Terminate() on it. We also make liberal use of Refresh() on the page.
Does anyone know of any other ways to increase the reliability of the fore mentioned tests?
We found that of all the browsers, Firefox was the fastest and most reliable with TestComplete. However, there are times that FF will simply stop loading a page with no warning. Going to the page and testing in the same conditions reveals no issues with the page itself.
The following are some of the things we did to increase reliability.
We currently completely shutdown (as in end the process of) Firefox after each test using the Sys.Process("firefox").Close(). When the Firefox process fails to close, then we call Terminate() on it. We also make liberal use of Refresh() on the page.
Does anyone know of any other ways to increase the reliability of the fore mentioned tests?
- You need to identify when the screen refreshes and then make a call to wait for the screen to redraw.
Our web pages have tabs on them, so after running the click method on a tab, I then call WaitForPageToRedraw(). Other situations are when navigating to different pages, or when clicking on a button that changes the UI to display a grid.
In one situation I have to put a delay in before calling WaitForPageToRedraw() due to a lag between clicking the Save and Close button and the screen beginning to redraw.