Share this page

# Create business process tests and flows

This section describes how to create, modify, and work with business process tests and flows.

Note:

Higher-level task: This task is part of a higher-level task. For details, see Plan business process tests and flows.

## Business process test, flow, and branches overview

Working with business process tests and flows is very similar to working with other OpenText Application Quality Management test types. The following highlights the differences.

For conceptual details on the Test Plan module for other OpenText Application Quality Management test types, see Test Plan.

Business process test | A business process test is a scenario comprising a sequence of business components or flows, designed to test a specific scenario in an application.
Business process flow | A flow is a type of test that comprises a logical set of business components, in a fixed sequence, that performs a specific task. Flows share the same functionality as business process tests (for example, iterations, parameters, and results). When designing flows, we recommend that you consider them "compound components." Flows cannot contain other flows. You can use a flow in multiple business process tests. When you modify a flow or any of its components, all business process tests containing that flow reflect that modification.
Branches | Branches are added to a business process test or flow as a control-type element, enabling you to instruct the test script how to proceed when a certain condition is met. Inside each branch, specify different actions for the test script to take, depending on application status during runtime. Each action the script takes is defined inside a branch option.

Back to top

## Create business process tests and flows

Follows the steps below to create and work with business process tests and flows.

1. Create test subjects.

2. Create business process tests and flows in the test plan tree

   1. In the Test Plan tree, right-click a folder, and select New Test.

   2. Fill in the Type field in the New Test dialog box, making sure to select one of the following test types:

      - BUSINESS-PROCESS to create a business process test
      - FLOW to create a flow

   3. Fill in the remaining fields in the New Test dialog box. For details, see Create tests.

   4. Save the test or flow.

3. Update business process tests and flows

   For each business process test or flow, you can update its details, attachments, parameters, and so on. Right-click a business process test or flow and select Test Details. The Test Details dialog box opens. For user interface details, see Test Details Dialog Box for Business Process Testing.

4. (Optional) Add branches to business process tests and flows.

   For task details, see Add branches.

5. Add content to business process tests and flows.

   Build the content of a business process test by:

   - Dragging business components and/or flows from the Select Components and Flows pane, and dropping them into the test in the Test Script tab.

   - Dragging business components and from the Select Components and Flows pane, and dropping them into the flow in the Test Script tab.

   Building the content can be done from both the Test Script Tab Grid and the Test Script Tab Canvas.

   Tip: In the Test Script Tab Grid, you can view information in an extended view. This lets you see a more comprehensive view of the test at a higher level, without drilling down by clicking various links.

   For user interface details, see Test Script Tab for Business Process Testing.

   Tip: From both the Test Script Tab Grid and the Test Script Tab Canvas, you can arrange the business components and flows into a logical testing order by:

   - Selecting business components and flows using the up and down arrow buttons in the toolbar.
   - Dragging and dropping the business components and flows.

   Example:

   The test for the loan request business process, RequestAndProcessLoans, may include components for logging in and logging out, and a flow, ProcessLoans, that contains the components for processing the loan request (CreateLoan, SearchLoan, and ApproveLoan):

6. (Optional) Record components for business process tests and flows.

   Users can create business process tests and flows automatically by navigating through applications. Actions taken while navigating are recorded as business components.

   For task details, see Record components into flows and business process tests.

7. (Optional) Learn business process tests and flows - optional

   BPT Packaged Apps Kit users can create business process tests and flows automatically by navigating through packaged apps.

   For task details, see Learn business process tests and flows.

8. (Optional) Request components.

   While designing a test or flow, you can request components be created and you can specify the details for creating the components. The component request can be included in your test or flow the same way as a regular component.

   1. In the Test Plan tree, select the business process test or flow for which you are requesting the component and click the Test Script tab.
   2. Click to open the Component Details dialog box.
   3. Rename the component request (from New Component Request), and fill in the relevant fields, such as Assigned to.
   4. Click OK. The new component request is displayed in the Test Script tab for the selected business process test or flow, and in the Component Tree pane under the Component Requests folder with a status of Not Implemented. For task details on creating a component from a component request, see the step Create business components in OpenText Application Quality Management.

   Tip: Unlike other components, requested components can be modified directly from the Test Plan module, unless the component request is contained within a flow in a business process test. (In this case, you can only view the component request from the business process test.)

   Note: You cannot automate component requests. You can add automation only after creating the corresponding component.

9. Set run conditions for the flow or business process test.

   For details, see Set run conditions for flows and business process tests.

10. Set failure conditions for components and flows.

    You can define whether a business process test run continues or ends if a specific business component or flow in the test fails.

    In the Test Script tab, click in the On Failure column for the business component. Select either Exit or Continue.

    For user interface details, see Test Script Tab for Business Process Testing.

    To set the default On Failure value, see Set default On Failure behavior to.

11. Group components and flows.

    In some cases, it may be helpful to iterate several business components or flows together as a group.

    In the Test Plan tree, click the Test Script tab. Select the components or flows you want to group, right-click, and select Grouping > Group.

    When iterating groups:

    - All items to be included in the group must have the same number of iterations and the same iteration range, or a warning message is displayed.

    - The number of iterations indicates the total number of value sets defined for the group.

    - The iteration range indicates the subset of iterations currently set for use when the test runs.

    For user interface details about creating groups, see Test Script Tab for Business Process Testing.

    For user interface details about group iterations, see Iteration Pages.

    For task details on iterating groups, see Define iterations for components, flows, and groups.

12. Validate tests.

    You can check your business process tests and flows to locate any component errors that could halt the successful running of the test or flow. Validating a business process test or flow in the Test Plan module checks all instances of the test or flow within all test sets.

    In the Test Plan tree, click the Test Script tab. Select the business process test or flow you want to validate. Click .

    If errors are found, modify the test as required. Repeat the validation check. If the errors have been resolved, a message is displayed indicating that the validation completed successfully.

    For user interface details, see Test Validation Results Dialog Box.

13. (Optional) Run manual tests from the Test Plan module.

    You can run business process tests manually from a printout. The printout details the relevant parameter values for each flow, group, iteration, component and step in the business process test. To generate the printout, select the business process test and run either of the following project reports from the Analysis menu in the Test Plan module:

    - Business Process Tests with Component Steps

    - Business Process Tests with Component Steps and Component Details

    Tip: You can also run these reports for auditing purposes.

14. Debug automated tests and flows from the Test Plan module.

    You can check whether automated components run together successfully in the test or flow by debugging the test or flow in the Test Plan module. You can check, for example, whether the component and flow order in the test is logical, or that components start where previous components in the test end.

    For task details, see Debug automated tests and flows.

Back to top

## How OpenText Application Quality Management calculates business process test and flow Statuses

The status of a test or flow is determined by the status of its business components. The component with the most severe status determines the test or flow status.

Example: Suppose you have a business process test that contains:

- 2 Ready components
- 1 Maintenance component
- 1 Under Development component
- 1 Error component
- 1 Not Implemented (requested) component

The test status is Error, because Error is the most severe status of a business component in the test.

Suppose you have a business process test that contains:

- 2 Ready components, one of which is outdated and moved to the Obsolete folder in the component tree.
- 1 Maintenance component
- 1 Under Development component
- 1 Error component
- 1 Not Implemented (requested) component

The test status is Outdated, because an obsolete component is more severe than the Error status.

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: