Relevant for: GUI and API tests
|RDC / Citrix||
When running UFT on a remote machine using a Remote Desktop Connection session (RDC) or using Citrix, if the computer on which the application is being tested is logged off or locked, the following problems may occur:
Workaround: If you are using Citrix or a Remote Desktop Connection session to run a test or component, make sure that the computer on which the application is being tested is not logged off or locked.
When running UFT tests or components on a local machine, if the computer on which the application is being tested is locked, your test run may fail.
Workaround: Install UFT on a virtual machine (without a screen saver or lock password), and start or schedule your run session on the virtual machine. Then you can lock your local computer without locking the virtual machine.
|Test Batch Runner / UAC||
It is not recommended to use Test Batch Runner with the UAC (User Account Control) feature set to ON.
|ALM Test Lab||
If you are running GUI tests from the ALM Test Lab, you must select the Allow connections from computers running any version of Remote Desktop option in the Windows Remote Settings (Control Panel > System > Remote Settings)
If your test run fails because of authentication errors:
|Calling a GUI test||
If you are running an API test that is stored in ALM and calls a GUI test, you must either ensure that UFT is open with a solution open, or you must close UFT and allow ALM to open it.
The test will not run if UFT is open with no solution.
|External .dll files||
When you manually add a reference to an external .dll, UFT prompts you to save it locally. To change your preference about a specific referenced file, remove the reference and add it again manually.
Running tests on remote machines using shared folders, may require adjusting the .NET 2.0 security settings.
Suggestion: Open the Control Panel and locate the Administrative Tools, either by browsing or through a search. In the list of Administrative Tools, look for the following entry: Microsoft .NET Framework 2.0 Configuration. If it is not present, you must install the .NET Framework 2.0 SDK.
|Validate Structure checkpoint||
The Validate Structure checkpoint fails if the expected value is a SOAP Fault and the Web Service call returns an UnsupportedMediaType status.
|Load Test mode||
When running an API test in Load Test mode, checkpoint verification in API test steps is not supported.
|Requirement: Active session and application||
The computer session must be active, and the application visible (and not minimized). for the steps to run successfully. This is because Insight uses data from the screen to compare to the images stored with your test.
If you are testing an application running on a remote computer, and you use a minimized Remote Desktop Connection window, these steps will fail.
Workaround: Use a different program (for example, Virtual Network Computing) instead of Remote Desktop Connection to run steps on a remote computer.
|Display size / zoom levels||
For Insight object identification to succeed, the display size defined in the operating system and the browser zoom levels (if working on a browser) must be the same when the test runs as they were when the objects were learned or recorded.
When using excluded areas in Insight, the included area must contain enough significant content to enable object recognition.
If the remaining content is not detailed enough, UFT may locate too few or too many matching controls on the screen.
Workaround: Do one or both of the following:
|Parent Browser objects||
When searching for an Insight object within a parent Browser test object, UFT searches within the selected browser tab, not in the whole browser window.
Insight is supported only on the primary monitor. Therefore, if you are working with dual monitors, make sure that your application is visible on the primary monitor when you use UFT for Insight test objects.