Recovery scenarios

Relevant for: GUI tests and components

Unexpected events, errors, and application crashes during a run session can disrupt your run session and distort results. This is a problem particularly when tests or components run unattended—the run pauses until you perform the operation needed to recover. To handle situations such as these, OpenText Functional Testing enables you to create recovery scenarios and associate them with specific tests or application areas. Recovery scenarios activate specific recovery operations when trigger events occur.

The 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. For example, you can instruct OpenText Functional Testing to detect a Printer out of paper message and recover the run session by clicking the OK button to close the message and continue running.

A recovery scenario consists of the following:

  • Trigger Event. The event that interrupts your run session. For example, a window that pops up on the screen, or a run error.

  • Recovery Operations. The operations to perform to enable the run session to continue after the trigger event interrupts the session. For example, clicking an OK button in a pop-up window, or restarting Microsoft Windows.

  • Post-Recovery Test Run Option. The instructions on how OpenText Functional Testing should proceed after the recovery operations are performed, and from which step to continue, if at all. You may want to restart the run from the beginning, or skip a step entirely and continue with the next step.

After you create recovery scenarios, you associate them with selected tests or components (via the application area) so that the appropriate scenarios can run if a trigger event occurs. You can prioritize the scenarios and set the order in which to apply the scenarios during the run session. You can also choose to disable specific scenarios, or all scenarios, that are associated with a test or application area.

You can also define which recovery scenarios will be used as the default scenario for all new tests.

For tests: You can associate, remove, enable, disable, prioritize, and view the properties of the recovery scenarios associated with a GUI test in the Solution Explorer. For details, see Solution Explorer Pane.

For components: You define recovery scenarios for components in the Recovery pane of the Additional Settings tab in the application area.

See also: