Known Issues - Running tests from ALM

Run results

Fast run results

If an ALM user manually changes the status of a test instance run, ALM creates fast run results to record the change of the test status. The fast run results are not valid run results files.

However, when you try to select results to open or delete in the Run Results Viewer or Run Results Deletion tool, the fast run results are available in the list.

ALM versions earlier than 12.50

If you run a UFT test and save the results in ALM, the result format of this run is the Run Results Viewer even if the HTML report is set in the Run Sessions pane of the Options dialog (Tools > Options > General tab > Run Sessions node).

Back to top

ALM versioning

When running a test from UFT with ALM 11.50 and later with an ALM project that supports versioning, the test instance run status will not be updated for tests that are checked out.

Back to top

External authentication

Accessing the ALM Test Plan

In order to run a UFT test or open a test, component, or application area stored in the Test Plan on an ALM server using external authentication, you must select the Non-interactive mode option in the Webgate Customization tool and select the external certificate in the same dialog.

For details about setting up certificates and the Webgate Customization tool, see the documentation for the Webgate Customization tool included with your ALM server.

Unable to connect

If a test running from an ALM server using external authentication fails with the message Unable to connect to the testing tool, make sure that your external certificate is selected in the Webgate Customization tool.

Note: Make sure that the certificate authority that issued your client certificate is added to the Trusted Root Certification Authorities for the current user.

For details, see the documentation for the Webgate Customization tool for your ALM server.

Back to top

Stopping a test in the middle of a run

When running a test set from the Test Lab module, if you stop a test set run in the middle of the run, and then immediately start another run, UFT behaves unexpectedly.

Workaround: Wait after stopping the test set run.

Back to top

Running API tests on Windows 2012 R2

Network COM+ access is not enabled by default on Windows 2012 R2, and is required for running API tests from ALM.

Enable it manually before running your API tests as follows:

  1. Browse to the Windows Add or Remove Programs control panel.

  2. Click Turn Windows features on or off.

  3. In the Add Roles and Features Wizard, click Server Roles, and then select Application Server.

  4. Expand the details of the child features, and select the COM+ Network Access option.

  5. Click Next until you complete the Windows Components wizard, and then click Install to install the features.

Back to top