I faced a Problem with error handling
If running a Test in Batch Mode and an Unexpected error comes which the script does not recognise and the script fails keeping the application window open.
There could be problems with the Next script as it would open another application window.
Gautam, according to my point of view this is more an advantage of batch mode than a disadvantage.
In "normal" mode the test execution would stop at the point the unexpected error occurs, whereas in batch mode the script terminates and gives control to the calling script.
That's fine for an unattended test run.
It's part of your test automation to ensure that the application is in a stable state when a test script starts (your test has to check if its initial conditions are given).
E.g. in my testing framework each single test checks if the application is started, ... before the "real" test starts.
And my controlling script (that calls the single tests) restarts the application everytime the previous called test failed. That's just to guarantee more robustness of my tests.
Long answer, slightly sliding into off-topic... [img]images/icons/wink.gif[/img]
Yes, please tone down the CAPS. The main disadvantage of batch testing is that it can make it more difficult / time consuming to diagnose script errors / defects caused from changes in your application. I like my scripts to stop at a point where a change in the application causes a context sensitive error. I can then quickly fix the script or take a screenshot and write a defect, then continue execution. I think this beats having to find the exact place in the script where the problem occurred and running up to a brake point to diagnose the issue later.