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 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.
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 may crash in a CAC environment. In such cases, uninstall the KB4103712 update to use UFT.
For more details, see the Microsoft support site: https://support.microsoft.com/en-us/help/4103712/windows-7-update-kb4103712.
|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:
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.
Do one of the following:
- Connect to ALM with administrator permissions immediately after installing UFT.
- Before connecting to ALM from UFT, connect to ALM using Internet Explorer or ALM Explorer. This enables you to download the ALM Client onto the Windows server using administrator privileges.
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.
|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 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 cannot lock resources on the SaaS server.
For example, in such situations, attachments to test plans on the ALM SaaS server cannot be locked.
To run UFT 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.
Note: The ALM WebGate Customization Tool was known as ALM Configuration Tool in UFT 14.0x and ALM 14 SaaS.
Running ALM tests from UFT on an ALM server that uses SSO is not supported when the UFT machine has no SSO credentials installed.
|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 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.
When the UFT Uft4Winrt service is running, you may need administrator privileges when first connecting to ALM.
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:
Go the following location on the ALM client machine: http:\\<ALM Platform server name>[<:port number>]/qcbin/Apps/
Click on the Webgate Customization Tool link and select Run.
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.
Click Save and then Close.
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.
Before you run tests remotely from ALM, you must perform the following prerequisites:
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 DOCM cross-domain support.
|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.
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 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.
To run a test or component from ALM, you must first invoke UFT at least once. Otherwise, ALM may be unable to open UFT.
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 test parameter from UFT 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 running API tests from ALM, using test parameters linked (in ALM) to data tables stored in ALM is not supported.
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.
When you save a resource to ALM (either from UFT 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 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.