Share this page

# Work with BPT Packaged Apps Kit

Available for BPT Packaged Apps Kit Users

BPT Packaged Apps Kit adds additional functionality to OpenText Application Quality Management and Business Process Testing that enables you to test packaged applications. This functionality includes features such as learning flows and business process tests, and also change detection.

In this topic:

## Prerequisites

To work with BPT Packaged Apps Kit:

- Make sure OpenText Functional Testing is installed on the client machine along with its SAP add-in and OpenText Application Quality Management plug-in.

- BPT Packaged Apps Kit is enabled in OpenText Application Quality Management Customization.

  For details about enabling BPT Packaged Apps Kit, see Configure Business Process Testing.

- Supported Apps: BPT Packaged Apps Kit supports SAP GUI and Fiori.

  Note: SAP Fiori is a technical preview. Learning flows and business process tests is supported; Change detection is not yet supported.

Note: When using BPT Packaged Apps Kit, it is best to work with only once instance of OpenText Application Quality Management open. Do not open multiple instances of OpenText Application Quality Management in multiple browsers or tabs.

Back to top

## Benefits

BPT Packaged Apps Kit includes the following benefits:

- BPT Packaged Apps Kit can automatically learn the actions you perform on your applications, and then generate a flow or business process test containing components based on the screens and transactions within your applications. You can reuse learned components instead of creating new components.

- BPT Packaged Apps Kit enables you to run tests and flows on applications in Change Detection mode. This enables you to determine how the applications have changed since the test or flow was built.

Back to top

## Roadmap

The roadmap with BPT Packaged Apps Kit includes the following additional phases:

Note: The actual workflow in an organization may differ for different projects, or at different stages of the application development life cycle. All stages in this workflow can be performed by a subject matter expert, without the involvement of an Automation Expert.

Phase | Description
--- | ---
Create flows and business process tests | You create flows and business process tests in the Test Plan module. For task details, see Create business process tests and flows.
Learn components | BPT Packaged Apps Kit enables you to learn the steps that comprise a transaction as you navigate your packaged app. BPT Packaged Apps Kit creates automated business components corresponding to screens and transactions in your app, and creates automated component steps based on the operations you perform. These components are then added to the flow or business process test. During the Learn process, you can insert checkpoints and output values. For task details, see Learn business process tests and flows.
Build tests from learned flows | In addition to business process tests that you learned, you can also build a business process test from the flows that were created in the Learn process. In addition, you can include other flows and business components with both manual and automated steps. For task details, see Create business process tests and flows.
Define run conditions | You can use run conditions to determine whether to run a component or flow, skip to the next component and continue, or end the run. This determination is based on a parameter's value and the run condition's definition. For task details, see Set run conditions for flows and business process tests.
Run tests in regular mode | You run a business process test containing learned components and flows as you would a regular business process test. For task details, see Run business process tests and flows.
Run tests in Change Detection mode | If your test includes flows learned automatically, or your test itself was learned automatically, you can run the test in Change Detection mode. BPT Packaged Apps Kit checks whether elements in your packaged app changed since the flow or test was learned. This enables you to later update your flows and tests to reflect these changes. For task details, see Run tests in change detection mode.
Resolve changes | When a test or flow that ran in Change Detection mode is complete, you can view a report detailing the status of each test, flow, business component, and component step in your test, including whether objects used in your steps have changed in your app. If changes were detected during the test run, you can view the changes in OpenText Functional Testing and OpenText Application Quality Management. You are offered a variety of options for resolving them, such as removing an obsolete step from a component, or reporting a defect. After you resolve the changes and update your flows and tests, you can run additional testing cycles to further test your app. For task details, see Run tests in change detection mode.

Back to top

## Work with BPT Packaged Apps Kit with support for SAP apps

The following steps describes how to work with BPT Packaged Apps Kit if your supported packaged apps include SAP apps.

1. Prerequisites: Make sure that the SAP add-in for OpenText Functional Testing is installed.

2. Configure OpenText Functional Testing to work with BPT Packaged Apps Kit features with support for SAP apps

   1. Open OpenText Functional Testing and add a GUI test to a solution.

   2. Select Tools > Options and click the SAP node. In the SAP pane, under SAP GUI for Windows > Record settings, ensure the following:

      - The Auto-parameterize table and grid controls check box is selected. This option ensures that Business Process Testing can learn table values during the Learn process.

      - The Record only the selected value when using a Possible Entries (F4) list check box is checked.

      - Under General > SAP GUI for Windows > Run settings ensure that the Session cleanup check box is not selected.

3. Understand how BPT Packaged Apps Kit creates components when learning SAP flows.

   For details, see How BPT Packaged Apps Kit creates components when learning SAP GUI flows.

Back to top

## How BPT Packaged Apps Kit creates components when learning SAP GUI flows

When BPT Packaged Apps Kit learns a flow or a business process test, it creates a new business component for each screen or sub-screen through which you navigate in your SAP GUI app. Each screen or sub-screen within a particular transaction is represented as a separate business component.

The name of a learned component is of the form <Transaction code>-<Screen name>. If the transaction code or screen name contains spaces or characters that are not valid in the names of business components, these characters are replaced by underscores (_). For example, if a learned component corresponds to the screen Create Sales Order: Initial Screen in the VA01 transaction, the component is named VA01-Create_Sales_Order_Initial_Screen.

If you navigate from one screen to a different screen or tab, and then return to the original screen, a new component is created with the same name as the component corresponding to the original screen, with a numerical suffix appended to differentiate between the components. For example, suppose the component corresponding to a screen is named VA01_Test. If you return to the screen, a new component is created named VA01_Test_01. Reusing existing components in your learned flow or business process test minimizes the number of learned components for similar or identical screens.

For each user operation within a screen that requires data specified by the user, an input component parameter is created for that step. the input component parameters that are created during the Learn process are automatically set as flow parameters. The value input during the Learn process is used as the default parameter value. For example, a parameter would be created for a value entered in a text field.

The name of an automatically generated parameter is the same as the name of the relevant field in the application. For example, in a Display Sales Order transaction, the parameter name of the order number would be Order. If a flow contains several components that have the same parameter name, an incremental suffix is added to subsequent parameter names (for example, Order_1, Order_2) in order to differentiate between them.

The description of a generated parameter includes the type of control and the name of the screen in which it appears, for example, "The 'Order' control is of type 'Edit Box'. The control is a part of the 'Display Sales Order: Initial Screen' screen."

If you add data to a table in your SAP app while learning a component, a component table parameter is created. Table parameters enable you to use one parameter for an entire table, rather than using separate parameters for each table cell. For details on working with table parameters, see Specify a table value .

Note:

- During the Learn process the table parameter saves the data only after you move the focus out of the table. If the table data is the last step in a learn process, ensure that you move the focus out of the table before stopping the learn.
- To create table parameters during the Learn process, you must enable OpenText Functional Testing to create table parameters. In OpenText Functional Testing, and a GUI test to the solution and select Tools > Options > GUI Testing > SAP > General node. Under SAP GUI for Windows > Record settings ensure that the Auto-parameterize table and grid controls check box is checked. For details, see Specify a table value .

If a screen contains a tab strip, one component is created for the common area on the screen, and a separate component is created for each tab opened. The status bar is included in each component created for the screen. For example, consider the screen below:

When you learn a flow or business process test, containing this screen, operations performed on the upper area of the screen containing the menus, toolbars, and common fields (such as Standard Order and Net value) comprise a single business component. Operations performed in each of the Sales, Item overview, Item detail, Ordering party, Procurement, Shipping, and Reason for rejection tabs result in the creation of separate business components.

Back to top

https://admhelp.microfocus.com Application Quality Management 8942
Tips to improve your search results... OpenText™ Application Quality Management Help Center OpenText™ Application Quality Management Help Center OpenText™ Application Quality Management Help 26.1 All View Local Help Center View Online Help Center Version: