Components with Automated Content

Use the Automation tab in the Business Components module to create or modify automated business component content either: 

  • As scripts, implemented in a testing tool such as UFT One (scripted GUI or API automation) or UFT Developer

  • In the form of keyword-driven steps and expected results (keyword GUI automation)

    Steps represent operations that should be performed on your application when you run the component in a business process test or flow. Each step is made up of an item (an object in the application or an operation), and an operation. The available items and operations are defined by the automation engineer in the object repository and the function libraries. These objects and operations can be saved in ALM, making them available for insertion into steps by the subject matter expert.

Note: Most of the information, examples, and images in this Help file focus specifically on working with keyword GUI automated components. However, much of the information also applies to scripted components (either scripted GUI or API).

When using the automated runner to run a business process test or flow in ALM, the steps or script defined in an automated component are performed.

Creating automated components consists of the following phases:

Phase

Description
Automation Type Selection

You create automation for a component when you select the automation type. After this phase, the component is accessible in the corresponding testing tool, such as UFT One.

Creating the automated component within ALM is typically done by the subject matter expert.
Content Automation Preparation

You prepare a component's content for automation, for example, by selecting an application area.

Preparing the automated component within ALM is typically done by the subject matter expert.

For conceptual details on creating application areas, see Application Area Overview.
Content Automation

You create steps. The steps represent the operations that are performed automatically on your application when you run the component using a testing tool.

After this phase, the steps are fully automated, and the automated component can run in an automatic runner without pausing.

Automating steps within ALM is typically done by the subject matter expert in conjunction with the automation engineer.

Business Process Testing provides the following types of automation.

Automation Type

Description
Keyword GUI automation

Enables you to create and modify automated keyword GUI steps in a Keyword view from within ALM.

For task details, see Work with keyword GUI automation.

Note: The Keyword view in ALM provides similar functionality to the Business Component Keyword View in UFT One. For a full description of the functionality provided in UFT One, see the Micro Focus Unified Functional Testing User Guide.

Scripted GUI automation

Enables you to launch UFT One to view and modify the automated scripted GUI and API steps. For task details, see How to Work with Scripted GUI and API Automation.
API automation

Enables you to launch UFT One or Service Test to view and modify the automated API steps. For task details, see How to Work with Scripted GUI and API Automation.

Note: API scripted automation is supported for Micro Focus 11.10 or later. For details, see the Micro Focus Service Test User Guide or the information about API testing in the Micro Focus Unified Functional Testing User Guide.
UFT Developer automation

Enables you to view and modify UFT Developer automation implementation. For task details, see How to Work with UFT Developer Automation.