Tip: If a testing tool is not installed, the button in the Automation tab is disabled.

Install the Unified Functional Testing Add-in for Business Process Testing on the client computer. The Unified Functional Testing Add-in for Business Process Testing is available from the Application Lifecycle Management Add-ins page (Help > Add-ins).

To be able to debug or run automated keyword GUI components, or view test results, make sure that UFT 12.00 or later is installed.

Automating components involves the creation of application areas, which provide access to the settings and resources required for a particular application.

Make sure that your application is ready to be tested, and all of the required automation resources have been prepared.

In UFT, if not yet connected, connect to the ALM project (for which you want to create the application area).

For details, see the information about connecting to ALM projects in the Micro Focus Unified Functional Testing User Guide.

Do one of the following:

Create a basic application area based on a default template in the ALM Test Resources module. The default application area template is stored in the System Application Areas subfolder and cannot be moved or modified. An automation engineer can then enhance the application area in UFT.

The default application area contains very limited operation options from which to choose when created automated steps.

Work with an automation engineer to create the application area in UFT.

In ALM, create and upload the application area resource in the Test Resources module. You can also create other resources with which the application area is associated, such as libraries, object repositories, and recovery scenarios in ALM (and associate them to the application area in UFT). For details, see the Micro Focus Application Lifecycle Management User Guide: How to Use Test Resources.

In UFT, define the settings and resource files that you want business components associated with the application area to use. By associating a component with an application area, the component is automatically linked to these settings and resource files.

A keyword GUI component must be associated with an application area to create steps for it, but you can also change the application area when required.

Changing an application area may affect the automated component and prevent it from running correctly. For example, if a step uses an object that is not contained in the object repository of the new application area, the step fails.

In the Keyword View pane, select an application area if the following message appears next to the toolbar buttons:

Choose an application area by clicking the 'Select Application Area' button

Each step is an operation to be performed, and is defined as a row in the Keyword View pane.

For each step you add or modify, you specify:

The item, such as an object from the application area's shared object repository, on which the step is performed.

The operation (keywords specified in the application area) to be performed on the item.

Any required values.

Output values.

Documentation, such as comments.

Save the steps.

Tip:

Since changes you make in the Keyword View pane are not saved automatically, it is recommended that you save them periodically.

A component is not fully automated until all of its steps are automated. For example, if you specify an Operation item with an Operation value of ManualStep, the automation is not yet complete. When running the component, there is a pause for user input.

Checkpoints compare the current value of a specified property with the expected value for that property, and can help identify whether your application is functioning correctly. For conceptual details, see Keyword GUI Automation Overview.

The checkpoint is visible and editable in the Checkpoint Properties dialog box in ALM, enabling you to view which properties are set to be checked during the run. For user interface details, see Checkpoint Properties Dialog Box.

Output Values

For steps that return a value, output values store settings that determine where the output value is stored and how it is used during the component run session. When the output value step is reached, each value set for output is retrieved and stored in the specified location for use later in the run session.

Tips to improve your search results...TOCALM Help CenterALM Help Center12.60AllView Local Help CenterView Online Help CenterbackGo back in browser historyforwardGo forward in browser historyRemove search highlightsnext topicGo to next topicprevious topicGo to previous topicPrint the current topicVersion(Undefined variable: _rscC_Basic_Variables.FloatingTocShow)