Known Issues - UFT and ALM

ALM and Windows security issues

The security settings in Windows 7, Windows Server 2008 R2, and Windows 2012 may prevent you from performing a UFT related installation, such as a patch installation, or connecting to an ALM project (either directly or from UFT).

This can occur when the UAC (User Account Control) option is set to ON, and you have not yet connected to an ALM project (if relevant).

Workaround: Temporarily turn off the UAC option. For details, see Known Issues - UFT Programs.

After disabling the UAC option as described above, perform the required installation or connect to ALM as usual. When you are finished, you can turn the User Account Control (UAC) option on again.

Back to top

Connecting to ALM on Windows 8.x

ALM versions earlier than 12.53

In Windows 8.x, when trying connecting to an ALM version earlier than 12.53 from UFT with the UAC turned off, you cannot connect to ALM.

Workaround: Run UFT as an administrator (even if you are the admin user).

Running UFT tests from ALM

When running a test in UFT from ALM on Windows 8 or higher, you must connect to the ALM server running Internet Explorer with Administrator permissions and with the following URL format:

http://myserver:8080/qcbin/start_a.jsp?common=true

Back to top

Connecting to ALM on Windows 10 or Windows Server 2016

  • Connecting to ALM via UFT or the Run Results Viewer on Windows 10 or Windows Server 2016 without administrative privileges is not supported.

    Workaround: Connect to ALM with Administrator permissions immediately after performing your UFT installation.

  • Running tests from ALM on UFT on computers running Windows 10 or Windows Server 2016 is not supported with servers running ALM version 14.00 or 12.53 can have unexpected results.

    Workaround: Connect to ALM in UFT at least once on the computer or register ALM in common mode using this URL: http://<ALM server URL>:8080/qcbin/start_a.jsp?Common=true

Back to top

Connecting to ALM 14.00 servers

  • When using ALM servers running version 14.00, after connecting to a server with your login credentials, you cannot switch to another user by clicking Disconnect and entering new login credentials.

    Start UFT again and enter the new credentials.

  • Before running tests from ALM servers running version 14.00, you should connect to ALM from UFT at least once or install the ALM Client in common registration mode from his URL on Internet Explorer: http://<ALM server URL>:8080/qcbin/start_a.jsp?Common=true.

  • When connecting to ALM 14.00 servers on computers running Windows Server 2012, you must cconnect from UFT at least once or install the ALM Client in common registration mode to ensure that all components from ALM are added correctly.

    The URL should be: http://<ALM host>:<port>/qcbin/start_a.jsp?common=true

Connecting to ALM servers using Secure Sign On (SSO)

  • You can connect to an ALM server using SSO using the command line with the following command prompt:

    UFT Path\bin>ALMConfigTool.exe /AuthUser=<user name> /AuthPass=<password>

    However, when using this command, the ALM Configuration tool still opens. You can close the tool as needed.

  • If you want to run a test from an ALM server using SSO on another computer containing only UFT (no SSO credentials installed) and running Windows 10 or Windows Server 2016, the test does not run.

First connection to ALM

The first time you connect to your ALM server, (either within UFT or through a browser) you must connect as an administrator.

This allows the machine to properly install the ALM client with the required connectivity. For all subsequent connections, you do not need to log in as administrator. This step is also required after installing ALM patches.

Back to top

ALM authentication

If there is a forward proxy with Basic Authentication between the server and client machines, before the first connection to an ALM platform, each ALM client must configure the proxy credentials by using the Webgate Customization Tool.

If you do not run WebGate, you may be unable to connect, or you may need to enter your credentials multiple times.

To run the tool:

  1. Go the following location on the ALM client machine: http:\\<ALM Platform server name>[<:port number>]/qcbin/Apps/

  2. Click on the Webgate Customization Tool link and select Run.

  3. In WebGate Customization, click in the Proxy Credentials area. Select the Use these credentials check box, and type values in the Proxy Username and Proxy Password boxes.

  4. Click Save and then Close.

Back to top

Switching ALM servers

If you are connected to an ALM server, and you want to connect to a different server, disconnect from the first ALM server, restart UFT, and then connect to the second server.

Back to top

Running tests remotely from ALM

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

  1. You must enable COM+ access. For details, see the Installation Guide.

  2. Change DCOM permissions and open firewall ports. For details, see the Installation Guide.

  3. Run RmtAgentFix.exe from the <Unified Functional Testing installation>\bin folder, or use the Additional Requirements Utility, which you open by selecting Start > Programs > HPE Software > HPEUnified Functional Testing > Tools > Additional Installation Requirements.

    This is due to a problem with opening DCOM permissions on Windows 7 and Windows Server 2008 R2.

  4. Disable User Account Control (UAC) in Windows and restart your computer before you first connect to ALM. For details, see Known Issues - UFT Programs.

Back to top

Documents saved in ALM

Locked ALM assets

If UFT closes unexpectedly while an asset is open from ALM, the asset may remained locked by ALM for more than fifteen minutes.

In some cases, you may be able to reopen UFT and reopen the test, but when trying to save it, you will receive an error message indicating that the test entity is already locked by you.

Workaround: Wait fifteen minutes or more and try again.

Renaming tests / components

Renaming a test or component from ALM may cause the test or component to behave unexpectedly.

Workaround: To rename a test or component, open it in UFT and rename it using the Save As option.

If the test or component has already been renamed from ALM, use the rename option again to restore the old name, and then use the Save As option in UFT.

Renaming a test parameter from UFT causes any run-time parameter values already set for this parameter in ALM to be lost.

Checkout from ALM

For tests or business components saved on ALM, if you perform a checkout from within ALM, it is not reflected in UFT for the current test—the test or business component still appears to be checked in.

Workaround: Close and reopen the test in UFT.

Back to top

QuickTest tests saved in ALM

If a test is stored in ALM, and was last modified using a version of QuickTest earlier than 9.5, it opens in read-only mode.

To edit the test, it must be upgraded to QuickTest 11.00 using the QuickTest Asset Upgrade Tool for ALM (found on the QuickTest 11.00 installation DVD).

Back to top

Adding documents stored in ALM to a solution

Testing documents that are part of the same solution cannot be stored in different ALM projects, domains, or servers.

Back to top

Working with non-Unicode ALM projects

ALM supports non-Unicode projects. If you are working with an ALM project that is not Unicode compliant:

  • You should not use Unicode values (such as the name of the test or component, the name of an application area, the default value of a test, action, or component parameter, method argument values, and so forth).

  • Data that is sent to UFT from ALM (such as values for test, action, or component parameters) is not Unicode compliant.

  • UFT results containing Unicode characters may appear corrupted in the ALM result grid. You can, however, open and view results containing Unicode characters in the UFTRun Results Viewer.

    For additional details on UFT Unicode issues, see Known Issues- Multilingual Applications.

Back to top

GUI testing: Running a GUI test from ALM

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

Back to top

GUI testing: Parameters names in the Data table

If the parameter names in your Global data table are identical to the parameter names in an external data table, running a test configuration with data table parameter mapping to other data table parameters causes unexpected results.

Example:  

If : Your Global data table parameters and Login and Password, and;

Your external data table parameters are Login, Password, Login_localized, and; Password_localized;

Then: A test configuration run with mapping from Login to Login_localized and Password to Password_localized will cause unexpected results.

Workaround: Split the external data table into multiple tables.

Back to top

GUI testing: Renaming parameters

Renaming a UFT test parameter from UFT will cause any run-time parameter values already set for this parameter in ALM to be lost.

Back to top

API testing: Changing licenses

While connected to an ALM project, if you change the available license for an API test, ALM continues to use the original license.

Workaround: Log out from your ALM project and restart Internet Explorer.

Back to top

API testing: Linking API test parameters

When running API tests from ALM, using test parameters linked (in ALM) to data tables stored in ALM is not supported.

Workaround:

  • Instead of associating test steps with test parameters, link the steps to an Excel data source added to the test.
  • When you add the data source to the test, select Allow other tools to override the data.
  • Then, in the ALM Test Plan, instruct ALM to overwrite this Excel with data tables stored in ALM. For details on instructing ALM to overwrite data sources, see the ALM documentation.

Back to top