I've created a Table Driven (Data-Driven) framework, by reading various articles and message forums. Currently the way I do error handing (let the scripts continue, log some message) is within the function that is being performed. Example on a AcxTable (QTP) I select a Row, the row did not get highlighted so I try it again. But I can't handle, things like pressing a button, and an unexpected window appears. From my readings this is supposed to be done in the driver script, not the utility scripts. Can somebody please explain how.
I just finished the Exception Handling thread, and what I want to implement is a way to handle common errors, like message boxes and let the tests continue to run and log some sort of event.
As I understand it, if a screen compare, unknown pop-up, or any error in the normal flow of the test occurs then an error handler is invoked which will compare the error to known error conditions and/or clear and record the error then terminate that TC, reset the environment and move on to the next test.
Success is the ability to go from one failure to another with no loss of enthusiasm.
~ Winston Churchill ~
Is this done in the main control loop in my driver script? Or do I have another script which is called by my driver script to handle any errors. I use QTP but I really don't like the Recovery Manager, and instead would like to handle any unexpected events with a vbs script.