Known Issues - UFT and ALM
The security settings in Windows 7, Windows Server 2008 R2, and Windows 2012 may prevent you from performing a UFT One related installation, such as a patch installation, or connecting to an ALM project (either directly or from UFT One).
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.
After disabling the UAC option as described above, perform the required installation or connect to ALM as usual. When you are finished, turn the User Account Control (UAC) option on again.
Windows 7 CAC environments
Additionally, if a Windows 7 machine has the Windows update KB4103712 installed, UFT One may crash in a CAC environment. In such cases, uninstall the KB4103712 update to use UFT One.
For more details, see the Microsoft support site: https://support.microsoft.com/en-us/help/4103712/windows-7-update-kb4103712.
Connecting to ALM on Windows Server machines
You must have administrator privileges on your Windows server machine to connect to ALM run tests in ALM from UFT One.
Do one of the following:
- Connect to ALM with administrator permissions immediately after installing UFT.
- Before connecting to ALM from UFT One, connect to ALM using Internet Explorer or ALM Explorer. This enables you to download the ALM Client onto the Windows server using administrator privileges.
|Earlier versions of ALM||
The first time you connect to an ALM server with an ALM version of 12.21 or earlier, (either within UFT One 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.
|Configuring ALM proxy credentials||
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:
|Default browser used for login||
When connecting to an ALM server, version 15.51 or later, that requires SSO authentication, authentication may use your default web browser.
You may want to avoid this, for example, if your default browser is Chromium Edge, which is not supported by ALM.
Use the WebGate Customization tool to set your own preference on the authentication browser setting. For details, see the Webgate Customization Tool readme.
To run UFT One tests from an ALM server where authentication must be configured, you must download the relevant ALM Webgate Customization Tool from the ALM server.
For example, you'll need the ALM Webgate Customization Tool when connecting to ALM via SSO.
Download the ALM Webgate Customization Tool from: http(s)://<ALM server>:<ALM port>/qcbin > Tools > ALM WebGate Customization
Configure your authentication using the Webgate Customization Tool UI, or silently via the command line. For more details, see the ALM Webgate Customization Tool Readme, provided together with the Webgate Customization Tool download.
Running ALM tests from UFT One on an ALM server that uses SSO is not supported when the UFT One machine has no SSO credentials installed.
To run ALM tests from UFT One using server-side execution on an ALM server that uses SSO, you must first perform the following:
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 One, and then connect to the second server.
When working with ALM 15.x and Windows 10, in order to add defects from the Run Results Viewer to the ALM client:
- Start the ALM client as an administrator.
- Register the ALM client with the following URL:
|Locked ALM assets||
If UFT One 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 One 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 One 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 One.
Renaming a test parameter from UFT One 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 One for the current test—the test or business component still appears to be checked in.
Workaround: Close and reopen the test in UFT One.
|Save test locally with results||When you open a GUI test stored on ALM and use File>Save As to save it locally, the save run results option is not supported.|
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).
Testing documents that are part of the same solution cannot be stored in different ALM projects, domains, or servers.
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 One from ALM (such as values for test, action, or component parameters) is not Unicode compliant.
UFT One results containing Unicode characters may appear corrupted in the ALM result grid. You can, however, open and view results containing Unicode characters in the UFT OneRun Results Viewer.
For additional details on UFT One Unicode issues, see Known issues - Multilingual applications.
|Linking to AUT Parameters in ALM 12.55 P2 or later||
When trying to link test parameters to AUT Parameters defined in ALM version 12.55 P2 or later, the Select ALM application parameters button is not displayed.
Install the ALM Client in common registration mode. Use the following URL in Internet Explorer: http://<ALM server URL>:8080/qcbin/start_a.jsp?Common=true.
|API tests: test parameters linked to ALM data tables||
When running API tests from ALM, using test parameters linked (in ALM) to data tables stored in ALM is not supported.
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.
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.
Renaming a UFT One test parameter from UFT One will cause any run-time parameter values already set for this parameter in ALM to be lost.
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.
When you save a resource to ALM (either from UFT One or using the Upload option from the ALM Test Resources module), and the resource file has a comma in the file name, the resource appears to be saved successfully, but the file is not actually uploaded to the ALM server.
For GUI testing: If you insert a call to an external action that is associated with a data table, and that data table was previously renamed or moved in the Test Resources module of Quality Center or ALM, UFT One tries to locate the data table in its original location.
Workaround: Save the test, close it, and reopen it.
If you are working with the Resources and Dependencies model, and the test containing the action you are renaming is stored the Test Plan module in ALM, the internal (default) action name is always displayed in the Used By Tab (Action Properties Dialog Box). This is true even if you rename the action.
|ALM versions earlier than 12.53||
In Windows 8.x, when trying connecting to an ALM version earlier than 12.53 from UFT One with the UAC turned off, you cannot connect to ALM.
Workaround: Run UFT One as an administrator (even if you are the admin user).
|Running UFT One tests from ALM||
When running a test in UFT One 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:
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 One again and enter the new credentials.
|Restore connection on startup||When connecting to ALM servers running version 14.00, the Restore connection on startup button is disabled.|
|First time connection||
Before running tests from ALM servers running version 14.00, do one of the following:
|Windows Server 2012||
When connecting to ALM 14.00 servers on computers running Windows Server 2012, you must connect from UFT One 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
|Working with virtual machines||
In an ALM SSO environment, if the name of a virtual machine does not match the current IP address, UFT One cannot lock resources on the SaaS server.
For example, in such situations, attachments to test plans on the ALM SaaS server cannot be locked.