StanST wrote:Afternoon:
Is logging out and closing the browser for each automated test case is good practice/protocol?
Is it the best practice to logout and close the browser session for each test case automated?
Thanks
Thanks for asking StanST.
This is a very good question, and a rather deep on.
What you are asking is, does a browser retain any state that can affect the subsequent test behavior.
The general answer is, yes, there is state information in the browser, as a consequence of using it as an executable.
You're correct, killing off the instance of eValid after a test and relaunching it DOES assure that the browser instance has nothing remembered.
But that does not guarantee that the cached files and cached cookies go away.
For that you need to use the Cache Manager, described here:
http://www.e-valid.com/Products/Documen ... ement.htmlBut, fair warning, if some other browser on the same machine is running, even if you delete the cache/cookies, you still have the [theoretical] possibility of some interference.
Every eValid script involves a sequence of commands to the eValid browser, as described here:
http://www.e-valid.com/Products/Documen ... iples.htmlTo really assure you have no residual memory you will need to study the commands in the script you are running repeatedly to see if any of them have a side-effect of storing data of some kind in the browser.
At the end of the day, we recommend closing and restarting as a sure preventive to cross-test data leakage.
-- eValid