Forum Discussion
I am not sure if you're doing this but if not, it should help.
One of the best practices for testing web applications in a browser is that after every test case, the browser should be restarted (to ensure proper initliazation of the browser state and prevent interference between test cases). I do that for all my test suites and the browsers perform as expected.
- Aerlock9 years agoOccasional Contributor
djadhav wrote:
I am not sure if you're doing this but if not, it should help.
One of the best practices for testing web applications in a browser is that after every test case, the browser should be restarted (to ensure proper initliazation of the browser state and prevent interference between test cases). I do that for all my test suites and the browsers perform as expected.
That is what I was doing already. Switching to reusing the same window seems to have resolved the issue. I'm not 100% sure that it is working this way because the suite has only been run a few times since I made the change yesterday. I also found references to a patch to address a memory issue in IE and other browsers. I have the patch but haven't applied it yet.
Related Content
- 11 years ago
Recent Discussions
- 12 hours ago