I have a very simple script (keyword) that logs onto an application, does a few validations and calls it a day. It is a foundation script I call to do other tests. (Certain User Profile)It runs fine and then a nice weekend away and I get back to work and it doesn't work again. sys.browser."iexplore" does not exist.This is a major sticking point when evaluating this application. It is consistently inconsistent.I re-recorded the script and it is working fine. That is contrary to our stated goal as we do not want to keep re recording tests.
Go to Solution.
Then perhaps when you come in on Monday, the browser isn't started so the test fails, but when you are running it during the week, the browser is there, having been left over from another test.
Best practice is to have the test or project open the browser that it needs and then close everything before it exits.
View solution in original post
It's difficult to troubleshoot if you've already fixed it. Next time it happens, let's get some more detailed information in the original post.
I did not fix the script I simply re-ran it.
I have been brought into to evaluate this tool and the previous user had the same issues. Did the application change?1. I rather doubt it - This is a test system amn Smart Bear has patches come out often.
Is there a Run Browser line in the test before this one that's failing?
No there is not....I have a script that cleans up all the sessions of explorer. I re-wrote the script and it is working a little more consistently.