In UFT, your test will be divided into "logical units" or "Business Processes" with the help of ACTIONS. Actions aid in the creation of a more modular and efficient script. When a script is first written, it just has one ACTION. However, depending on your needs, you can add more Actions to your Micro Focus UFT Script.

Actions are divided into two categories:

• Reusable Actions: Actions that can be reused in other tests. They can be used numerous times in the same Test Script.
• Non-Reusable Actions: Actions that aren't reusable can't be used in other tests. They can only be called once in the same script. When an action becomes large, it's a good idea to split it out. You have two options for splitting an EXISTING activity.
  • The selected action is split into two sibling actions because they are independent of each other.
  • Nested Action splits the chosen action into a parent action, the last step of which invokes the second, child action.

Importing Actions into a Test can be done in two ways:

• Call to COPY of an Action: When you make a Copy of an Action, the action is duplicated in its entirety into the calling test, including checkpoints, parameterization, and the relevant action tab in the Data Table. You can make modifications to a copied action without affecting or being affected by any other test when you insert a copy of an existing action. Both reusable and non-reusable actions can be duplicated.
• Call to an EXISTING Action: In the calling test, calls to actions are read-only. Only the test in which they were created can be changed. Allows you to reuse the same action across multiple tests and simplifies test maintenance. Only "Reusable" actions are AVAILABLE for calls.