Known Issues - Running tests from ALM

This topic describes known issues when running tests from ALM.

GUI testing: Running a GUI test from ALM

To run a test or component from ALM, you must first invoke UFT One at least once. Otherwise, ALM may be unable to open UFT One.

Running tests remotely from ALM

Prerequisites

Before you run tests remotely from ALM, you must perform the following prerequisites:

You must enable COM+ access. For details, see the UFT One Installation Guide.
Change DCOM permissions and open firewall ports. For details, see the UFT One Installation Guide.
Run RmtAgentFix.exe from the <UFT One installation folder>\bin folder, or use the Additional Requirements Utility, which you open by selecting Start > Programs > Micro Focus > Micro Focus UFT One > Tools > Additional Installation Requirements.
Disable User Account Control (UAC) in Windows and restart your computer before you first connect to ALM.

Cross-domain support

Running tests remotely across domains, such as calling tests from a local ALM client to run on an AWS machine, is not supported due to limitations in DCOM cross-domain support.

ALM Lab Service

To run UFT One tests remotely using the ALM Lab service, use one of the following:

The UFT One option to Enable testing on locked, logged off, or disconnected remote computers. For details, see Run a test using UFT One installed on a remote computer.
The Auto Login module on the ALM Lab Service.

Using both of these options together results in the UFT One machine becoming unusable to the ALM Lab Service.

Therefore, if you set this UFT One option, install ALM Lab Service without the Auto Login module, or modify the installation to remove this module.

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 One 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).

ALM versioning

When running a test from UFT One 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.

External authentication

Accessing the ALM Test Plan

To run a UFT One 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.

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 One behaves unexpectedly.

Workaround: Wait after stopping the test set run.

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:

Browse to the Windows Add or Remove Programs control panel.
Click Turn Windows features on or off.
In the Add Roles and Features Wizard, click Server Roles, and then select Application Server.
Expand the details of the child features, and select the COM+ Network Access option.
Click Next until you complete the Windows Components wizard, and then click Install to install the features.

Running an API test with an Excel data source

When running an API test that is configured to use an Excel data source, you may encounter the following error: "Unable to fetch data from <file path>: file not found."

Possible cause: The test is configured to Link to the Excel file in its original location, which is currently not accessible to the test.

Solution: Configure the test to make a local copy of the Excel file:

Open the Change Excel Data Source dialog box:

Open the API test, select the main node of the existing data source, and in the Properties pane, click Change Excel File.
In the File location option, select Make a copy of the Excel file.

Running a test with an Excel data source that contains structured references

Structured references in an Excel data source file appear as N/A in the ALM Resource Viewer. If you run a test that is configured to use such a file, the test may fail.

Running a BPT test from ALM

UFT One versions 2021 and earlier:

Running BPT tests containing API components is not supported when running from an ALM server version 15.0 or later that requires SSO authentication with Approval ID mode.

Using Azure DevOps Server to run UFT One tests from ALM or ALM Lab Management

Using Azure DevOps Server to run UFT One tests from an ALM server version 15.0 or later that requires SSO authentication is not supported.