Unexpected events, errors, and application crashes during a run session can disrupt your run session and distort results. This is a problem particularly when running components unattended—the component is suspended until you perform the operation needed to recover. The Recovery Scenario Manager provides a wizard that guides you through the process of defining a recovery scenario—a definition of an unexpected event and the operation(s) necessary to recover the run session. For example, you can instruct QuickTest to detect a Printer out of paper message and recover the run session by clicking the OK button to close the message and continue the component. Recovery scenario consists of :-
- Trigger Event—The event that interrupts your run session. For example, a window that may pop up on screen, or a QuickTest run error.
- Recovery Operation(s)—The operation(s) that need to be performed in order to continue running the component. For example, clicking an OK button in a pop-up window, or restarting Microsoft Windows.
- Post-Recovery Test Run Option—The instructions on how QuickTest should proceed once the recovery operations have been performed, and from which point in the component QuickTest should continue, if at all. For example, you may want to restart a component from the beginning, or skip a step entirely and continue with the next step in the component.
2 Comments:
Nice site. I am going through the pages on your site. Right now I am trying to get practice on Recovery Scenario. I have a parameterized login/password script for Mercury Flight application. One login's password is missing. I went through all the steps that the QTP help files tells me to do. I run the script. Iteration 1 and 2 run fine (have uid/pwd). Iteration 3 has no pwd. Popup comes up but the recover scenario does not kick in. The scenario is set as default and timeout is set at 10ms. I can't see why/where it issue is.
Can you help with this situation?
Brijesh, please update the Recovery Scenario document and tie it into Recovery Scenario settings and such. The recovery scenario recorded needs to be saved (how and where), made default (local test or for all), timing settings, etc.
Post a Comment