Recovery scenario is used to handle unexpected situations
that might occur while the test is running like exceptions and Runtime Errors.
Recovery Scenario Manager provides a wizard that guides you through the process of defining a recovery scenario, which includes a definition of an unexpected event and the operations necessary to recover the run session. The Recovery Scenario Mechanism enables you to instruct Quickest to recover from unexpected events and errors that occur in your testing environment during a run session.
We can handle pop-up window, object state, test run error, application crash exceptions and many more. Recovery Scenario is used only for unpredictable events or events that you cannot synchronize with a specific step in your component. Predictable events and errors can be handled with user defined functional and conditional statements but in case of unpredictable events we need to rely on Recovery Scenarios.
A recovery scenario has three major steps:
Recovery Scenario Manager provides a wizard that guides you through the process of defining a recovery scenario, which includes a definition of an unexpected event and the operations necessary to recover the run session. The Recovery Scenario Mechanism enables you to instruct Quickest to recover from unexpected events and errors that occur in your testing environment during a run session.
We can handle pop-up window, object state, test run error, application crash exceptions and many more. Recovery Scenario is used only for unpredictable events or events that you cannot synchronize with a specific step in your component. Predictable events and errors can be handled with user defined functional and conditional statements but in case of unpredictable events we need to rely on Recovery Scenarios.
A recovery scenario has three major steps:
- 1.Trigger Event: The event that interrupts your run session. E.g., a window that may pop up on screen, or a Quick Test run error, Object State or Application Crash.
- 2.Recovery Operations: The operations to perform to enable Quick Test to continue running the test after the trigger event interrupts the run session. For example, Keyboard or Mouse Operation (clicking an OK button in a pop-up window), Close Application Process, Function call or Restarting Microsoft Windows.
- 3.Post-Recovery Test Run Operations: The instructions on how Quick Test should precede after the recovery operations have been performed, and from which point in the test Quick Test should continue, if at all. For example, you may want to restart a test from the beginning, or skip a step entirely and continue with the next step in the test.
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.
Extension for recovery scenario files is .qrs
No comments:
Post a Comment