QuickTest Professional Recovery Scenarios are summarized in the below mentioned points with 3 "easy to understand" examples.
1)
With "Recovery Scenario Manager" you can
a) create and edit recovery files,
b) create and manage the recovery scenarios stored in those files.
2)
A unique icon corresponds to a recovery scenario that indicates its type.
3)
Each recovery scenario is represented by an icon that indicates its type.
4)
You are guided step-by-step, through the process of creating a recovery scenario by Recovery Scenario Wizard.
5)
You start by defining the trigger event. [4 trigger types are there Pop-up window, Object state, Test run error, Application crash]
6)
After that you specify the recovery operation(s) [Recovery Operation can be Keyboard or mouse operation, Close application process, Function call, Restart Microsoft Windows]
When using Function call, Functions have to be defined using a prototype syntax, which is different for each trigger type.(See QTP User Guide.)
7)
Then you select a post-recovery test run operation. [Which can be Repeat current step and continue, Proceed to next step, Proceed to next action or component iteration, Proceed to next test iteration, Restart current test run, Stop the test run]
8)
The recovery file is saved in the specific location with the file extension .qrs.
9)
Properties for any defined recovery scenario can be viewed from Recovery Scenario Properties dialog box
10)
During the run session, QuickTest ignores deleted recovery scenario that is associated with a test or component.
11)
You can copy recovery scenarios from one recovery scenario file to another.
12)
The scenarios can be prioritized so that QuickTest applies the scenarios during the run session in a order of priority.
13)
Some or all of the scenarios can be disabled.
14)
Recovery Scenario(s) can be set as default for all new tests.
15)
Go to File > Settings, the Test Settings dialog box opens. Select the Recovery tab.
You can edit a recovery scenario file path by clicking the path once to highlight it, and then clicking it again to enter edit mode.
16)
In the Recovery tab itself you can define when the recovery mechanism is activated:
On every step.
On error
Never.
17)
You can use the Recovery object to control the recovery mechanism programmatically during the run session.