This task describes how to work with business process tests and flows using Business Process Testing.
This task is similar to the same task for other ALMtest types, but includes modified steps relevant for Business Process Testing. For task details on working in the Test Plan module for other ALMtest types, see the Micro Focus Application Lifecycle Management User Guide
: How to Plan Tests in ALM.
This task is part of a higher-level task. For details, see Work with Business Process Testing.
Create a test plan tree of test subject folders, tests, and flows.
You define the details and description of a test, and then add content to the test structure by adding a sequence of business components and/or flows for a specific business process. Similarly, you can define the details and description of a flow, and then add content to the flow structure by adding a sequence of business components.
For task details, see How to Create Business Process Tests and Flows.
To make tests and flows more flexible, you can include parameters in business component steps, and make them available to your tests and flows. The business components and flows can pass variable values between each other.
You can define input and output parameters for flows.
You can define only input parameters for business process tests.
For task details, see How to Create Parameters.
You can run the same test or flow iteratively (repeatedly). Each run is called an iteration, and can access different parameter values.
For task details, see How to Set Data for Iterations.
To run tests for different use-cases, you can define test configurations. This enables you to run the same test under different scenarios, using different sets of data.
In addition to accessing static data (data supplied directly within ALM), test configurations for Business Process Testing can also access dynamic data (data supplied from an external data table).
For task details, see
How to Work with Test Configurations.
Link business process testing criteria (tests, flows, and components) with requirements in the requirements tree. By defining requirements coverage for business process testing criteria, you keep track of the relationship between the tests and flows in your test plan and your original requirements.
For task details, see How to Create Coverage by Criteria.
Link a business process test or flow to specific defects. This is useful, for example, when a new test is created specifically for a known defect. By creating a link you can determine if the test should run based on the status of the defect. For user interface details, see
Linked Defects/Entities Page.
Analyze the test plan by generating reports and graphs.
For details on analysis tools in ALM, see
How to Analyze Data in ALM.
Debug a test or flow by running in debug mode.
For user interface details, see Test and Flow Debugging User Interface.
After your test plan has been reviewed and approved, you can create a baseline. A baseline provides you with a snapshot of your test plan at a specific point in time. Use a baseline to mark any significant milestone in the application lifecycle. The baseline then serves as a point of reference against which changes can be compared. For task details, see
How to Use Libraries and Baselines in ALM.