Recovery Scenarios in QTP in Testing

You can instruct Quick Test to recover from unexpected events and errors that occur in your testing environment during a run session that disrupt your run session and disrupts results. This is a problem particularly when running tests or components unattended; the test or component is suspended until you perform the operation necessary to recover.

The Recovery Scenario Manager provides a wizard that guides you through the process of defining a recovery scenario.

Recovery-scenario.jpg

A recovery scenario consists of the following

Trigger Event: The event that interrupts your run session. For example a window that may pop up on the screen or a Quick Test run error.

Trigger-Event.jpg

Recovery Operation: The operation that must be performed to continue running the test. For example clicking an OK button in a pop-up window or restarting Microsoft Windows.

Recovery-Operation.jpg

Post Recovery Test Run Option: The instructions on how Quick Test should proceed once the recovery operations have been performed and from which point in the test or component Quick Test should continue if at all. For example you may want to restart a test or component from the beginning or skip a step entirely and continue with the next step in test.

Post-Recovery-Option.jpg

Recovery scenarios are saved in recovery scenario files. A recovery scenario file is a logical collection of recovery scenarios, grouped according to your own specific requirements. To instruct Quick Test to perform a recovery scenario during a run session you must first associate the recovery scenario with that test. A test can have any number of recovery scenarios associated with it.