Actions in GUI Testing

Relevant for: GUI tests only

In a GUI test, each test is comprised of actions. An action is a separate modular test script, including all of the steps in that action, and any objects in its local object repository and any associated shared object repositories.

Actions divide your test into logical units such as:

  • The main sections of a web site

  • Specific activities you perform in your applications

The actions used in the test, and the order in which they are run, are displayed in the canvas. For details, see The Canvas.

Tip: Create tests that call multiple actions to make your test more logical, modular, and efficient. For example, separate your actions by the main sections of a Web site, or specific activities that you perform in your application.

UFT One provides the following types of actions:

Action type Description
Reusable actions

  • Default type.

  • Can be called multiple times by the local test and other tests.

  • Must be updated from the original test.

  • Can be marked as non-reusable to change its type.
Non-reusable actions

  • Can be called only once, and in the local test.

  • Can be copied.

  • Can be marked as reusable to change its type.
External

  • Stored with another test.

  • Read-only in the calling test.

    You can choose to use a local, editable copy of the Data pane information.
Nested

  • Called from another action

See also: