Select Trigger Event Page

Relevant for: GUI tests and components

This page enables you to define the event type that triggers the recovery scenario, and the way in which OpenText Functional Testing recognizes the event.

Wizard map

The Recovery Scenario Wizard contains:

Welcome > Select Trigger Event Page > (Specify Pop-up Window Conditions Page) > (Select Object Page) > (Set Object Properties and Values Page) > (Select Test Run Error Page) > (Select Processes Page) > Recovery Operations Page > Recovery Operation Page > (Recovery Operation - Click Button or Press Key Page) > (Recovery Operation - Close Processes Page) > (Recovery Operation - Function Call Screen) > Post-Recovery Test Run Options Page > Name and Description Page > Completing the Recovery Scenario Wizard Page

Note: Pages that are in parentheses open according to the option selected in the previous page. Therefore, not all pages are displayed for every option.
Important information

  • The set of recovery operations is performed for each occurrence of the trigger event criteria.

    Example: If you define a specific object state, and two objects match this state, the set of recovery operations is performed two times, once for each object that matches the specified state.

  • The recovery mechanism does not handle triggers that occur in the last step of a test or component. If you need to recover from an unexpected event or error that may occur in the last step, you can do this by adding an extra step to the end of your test or component.
  • See also Known issues - Run sessions in the Known Issues topic.

User interface elements are described below:

UI Elements

Description
Pop-up window

Detects a pop-up window and identifies it according to the window title and textual content.

Example: A message box may open during a run session, indicating that the printer is out of paper. OpenText Functional Testing can detect this window and activate a defined recovery scenario to continue the run session.
Object state

Detects a specific test object state and identifies it according to its property values and the property values of all its ancestors. Note that an object is identified only by its property values, and not by its class.

Example: A specific button in a dialog box may be unavailable when a specific process is open. OpenText Functional Testing can detect the object property state of the button that occurs when this problematic process is open and activate a defined recovery scenario to close the process and continue the run session.
Test run error

Detects a run error and identifies it by a failed return value from a method.

Example: OpenText Functional Testing may not be able to identify a menu item specified in the method argument, due to the fact that the menu item is not available at a specific point during the run session. OpenText Functional Testing can detect this run error and activate a defined recovery scenario to continue the run session.
Application crash

Detects an application crash and identifies it according to a predefined list of applications.

Example: A secondary application may crash when a certain step is performed in the run session. You want to be sure that the run session does not fail because of this crash, which may indicate a different problem with your application. OpenText Functional Testing can detect this application crash and activate a defined recovery scenario to continue the run session.