How to Run Automated Business Process Tests and Flows

This task describes how to run automated business process tests and flows.

1. Prerequisites

   • Before running a test within a test set, you can specify the values for any test parameters defined for the test. If you do not specify values, and valid default values have not been specified, the test run may fail.

   • Before you run an automated test on a host computer, ensure that the relevant testing tool on the host allows ALM to run tests.

     Example: Example

     To enable ALM access to a specific UFT client, open UFT on the host computer, select Tools > Options > GUI Testing > Test Runs, and ensure that Allow other HP products to run tests and components is selected.

   • Test results are, by default, saved in ALM. When running an automated test from within ALM you can avoid saving large test results by setting the UPLOAD_RESULTS_AFTER_TEST_RUN site parameter. For details, see the HPE Application Lifecycle Management Administrator Guide: Setting ALM Configuration Parameters.

   • When running default test sets on remote hosts, ALM communicates directly with the testing host to initiate the test. See your testing tool documentation for information about what ports must be opened and what other security settings must be adjusted to enable communication.

   • To run a UFT component from ALM, you must have the necessary ALM permissions. For details, see the HPE Application Lifecycle Management Administrator Guide: Managing User Groups and Permissions.

   • When you run a UFT business process test from ALM, the test run may be influenced by UFT Remote Agent settings on the UFT computer. For details on the UFT Remote Agent, see the HPE Unified Functional Testing User Guide.

   • In preparation for running UFT business process tests remotely , you must first register your ALM client in common mode on the remote machine. For more information, refer to the HPE Application Lifecycle Management Installation and Upgrade Guide.

     Note: To run a UFT business process test on a remote Windows 2012 machine, if the COM+ Network Access feature is not installed, you must restart the Windows 2012 remote machine after registration.

2. Debug tests and flows - optional

   Debug automated tests and flows to make sure that they run properly. For task details on debugging, see How to Debug Tests and Flows Containing Automated Components.

3. 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.

4. Determine if tests and flows should be run in change detection mode

   If you have BPT Packaged Apps Kit enabled, you can run automated tests containing learned flows in change detection mode. This enables you to determine if the packaged app being tested has been modified. For task details on detecting changes, see How to Run Tests in Change Detection Mode.

   Tip: 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.

5. Use the Automatic Runner to run the tests

   You can run manual and automated tests automatically on your machine or on remote hosts using the Automatic Runner.

   In the Test Lab module > Test Sets tab, use one of the following:

   • Select a test set that includes one or more automated tests and click the Run Test Set button.

   • To run selected tests, select a test set and click the Execution Grid tab or Execution Flow tab. Select one or more tests and click the Run button.

   • To run only manual tests, select the tests and click the Run button. In the Manual Test Run dialog box, select Automatic Runner and click OK.

   Notes

   • Dynamic dates are converted to the actual dates they represent.

   • If running an automatic test that contains component requests with manual implementations, those component requests are ignored during the run.

   For user interface details on the Automatic Runner, see the HPE Application Lifecycle Management User Guide: Automatic Runner Dialog Box.

6. Resolve detected changes

   If you have BPT Packaged Apps Kit enabled, and you ran the business process test or flow in change detection mode, you can resolve changes detected in the packaged app during the run. For task details on resolving changes, see How to View and Resolve Detected Changes.

7. View run results

   After you run the test or flow from the Test Lab module, you can view the results in various formats:

   • View results in the Test Lab module. You can view the results of the latest test run in the Test Lab module > Execution Grid > Last Run Report tab. This pane lists each step of all the business components in the test, and, where applicable, the summarized results of main events reported by the testing tool.

     For user interface details on the Last Run Report tab, see the HPE Application Lifecycle Management User Guide: Execution Grid Tab.

     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.

   • View the execution log. You can view details about the automatic test execution after execution is complete in the Automatic Runner dialog box > Run > View Execution Log. For user interface details, see the HPE Application Lifecycle Management User Guide: Execution Log Dialog Box.

   • View UFT reports. If you have Unified Functional Testing or the Unified Functional Testing Add-in for Business Process Testing installed on your computer, you can view a complete UFT report. The hierarchical report contains details on all the steps for all the different iterations and business components within the automated test run. The add-ins are available from the HPE Application Lifecycle Management Add-ins page (Help > Add-ins).

     From the Test Lab module > Execution Grid tab > Last Run Report tab, click the link to the report about each iteration in the Status column of the pane. The Run Results Viewer opens.

     For details on viewing and analyzing the results of tests in the Run Results Viewer, see the HPE Unified Functional Testing User Guide.