This task describes how to run business process tests and flows with one or more manual components.
This task is part of a higher-level task. For details, see Working with Business Process Testing.
Add iterations to business process tests and flows - optional
In the Test Lab module, you can determine how many times a business process test runs (iterates) and with what data. For task details on iterating tests, see How to Set Data for Iterations.
Tip: Parameter values can also be provided using the Test Configurations tab in the Test Plan module.
Use the Manual Runner or Sprinter to run the manual tests
Run your tests and flows using Sprinter or the Manual Runner.
For general task details on running tests manually, see the Micro Focus Application Lifecycle Management User Guide
: How to Run Tests Manually.
For user interface details on the Manual Runner for Business Process Testing, see Manual Runner Wizard for Business Process Testing.
BPT Packaged Apps Kit users can run tests and flows in change detection mode, to see if changes were made to the packaged app since the test or flow was created/last modified. Tests and flows that are run in Change Detection mode run only the first iteration of the selected range of iterations of any component, flow, or test, even if multiple iterations are defined. For details about detecting changes, see How to Run Tests in Change Detection Mode.
View and analyze test results
You can view the results of the latest test run in the Test Lab module in the Last Run Report tab at the bottom of the Execution Grid. This pane lists each step of all the business components in the test.
For user interface details on the Last Run Report tab, see the Micro Focus Application Lifecycle Management User Guide
: Execution Grid Tab.
Note: When a test or flow run ends, the parameters displayed in Last Run Report show the date used in the run and not the dynamic date value. Dynamic dates are converted to the actual dates they represent.
Tip: For samples of how to create graphs for Business Process Testing framework test run metrics, see this KB article.