Thanks for the answer. I hit another issue.
Used the batch runner. As the first test updates/inserts values into the global data table to pass it between actions, I think the test becomes an unsaved one after it runs; then when test batch runner tries to go to the next test in the batch, it could not...saying "Unable to close unsaved test".
I checked test run settings.. etc. Is there any way, we can tell the test to save before closing after a run. Or is there any (script) programmatic way to do this.
For solution 2, we do not want to close the browser window after a test-run. In other words, simply open a new browser every time the test runs ignoring the existing browser windows.
Used the batch runner. As the first test updates/inserts values into the global data table to pass it between actions, I think the test becomes an unsaved one after it runs; then when test batch runner tries to go to the next test in the batch, it could not...saying "Unable to close unsaved test".
I checked test run settings.. etc. Is there any way, we can tell the test to save before closing after a run. Or is there any (script) programmatic way to do this.
For solution 2, we do not want to close the browser window after a test-run. In other words, simply open a new browser every time the test runs ignoring the existing browser windows.