Relevant for: GUI tests only
In a GUI test, each test is comprised of calls to 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.
Each new test contains a call to a single action. Add calls to other new or existing actions, or copies of actions, both in the same or a different test. Ideally, each action should contain no more than a few dozen test steps.
The actions used in the test, and the order in which they are run, are displayed in 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 provides the following types of actions: