Relevant for: GUI and API tests
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.
|Citrix XenApp support||
If you are testing applications launched by Citrix XenApp, UFT must also be launched by Citrix XenApp.
Logged off RDC / Citrix
If you are running UFT on a remote machine using Remote Desktop Connection (RDC) or Citrix, we recommend not logging off your remote session.
Logging off your remote session while UFT is running may cause the following issues to occur:
|Multi-use remote credentials||
If you are running UFT and your application on a remote computer that supports multiple users logging in with the same username and password, we recommend not disconnecting from the remote computer.
In such cases, disconnecting and reconnecting will open a new user session, and your UFT run session may be lost.
Keep your connection open to retain your UFT session and run results.
|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.
|Calling an API test||
If your API test is called by a GUI test, values received from the API test output parameters are not supported as values for variables defined in functions in your GUI test.
|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.
The following known issues exist when running tests in parallel using the ParallelRunner tool.
Edge (UFT versions 14.51 and higher)
The ParallelRunner tool can run only one Edge browser at a time. Therefore, if you have multiple tests running simultaneously, only one of them can be running on Edge.
Web 2.0 toolkits
All Web 2.0 toolkits (ASP .NET AJAX, Dojo, Ext-JS, GWT, jQueryUI, SiebelOpenUI, and YahooUI), are not supported when using ParallelRunner.
Automation object model
UFT's automation object model is not supported for tests run using the ParallelRunner tool.
|Specific test objects and methods||
When running a web script using UFT's ParallelRunner, the .object method is not supported when Internet Explorer is running in a documentMode below 8.
WebFile objects are not supported for parallel execution.
Browsers launched by the SystemUtil.Run method may have unexpected results when running tests in parallel.
We recommend using the WebUtil.LaunchBrowser method instead.
To view the ParallelRunner run results in Internet Explorer, use an Internet Explorer version 10 and higher.
Run results with device monitoring graphs do not show red lines indicating the time stamp, when opened in Safari on a Mac machine. To view these red lines, use a different browser to view the run results.
Device system monitoring
Device system monitoring is not displayed in HTML run results graphs. Instead, to view system monitoring data for device tests run in parallel, check the log file linked from the run results.
Device reservations and release
Insight / OCR / highlight
Parallel testing on mobile devices may fail when the test uses Insight objects, or employs the OCR or highlight mechanisms.
Workaround: For Insight objects or the OCR mechanism, arrange the remote access windows displaying the devices in parallel so that they do not overlap.
|Using programmatic descriptions||
When running in Maintenance Mode, if a step contains a programmatic description for an object that is not found in an application, it may take a while for Maintenance Mode to indicate there is a problem. If you use the option to point to the object, it may take a while for Maintenance Mode to reopen afterward.
|Objects without mandatory or assistive properties||
When the Maintenance Run Wizard cannot find an object, and the test object description for that object does not have any mandatory or assistive properties (it is identified only by its ordinal identifier, such as a Browser test object), then when you point to the object, the wizard is unable to fix the problem and displays a message that the object you pointed to has a test object description that is similar to the object that UFT could not identify.
Workaround: Use the Update from Application option in the Object Repository window (for objects in the local respiratory) or in the Object Repository Manager (for objects in a shared object repository) to fix the test object description.
|Updating a step by pointing to a different object class||
When the Maintenance Run Wizard cannot find an object in the application, and you point to a different object class to replace it, the Maintenance Run Wizard offers to add a step with that object and the object's default method. However, the wizard does not insert any method arguments for the step. If the step method has required arguments and you accept the step that the Maintenance Run Wizard proposes without modifying it, the step fails when you run it.
Workaround: Enter valid method arguments for the step.
|Updating XPath or CSS properties||
When running in Maintenance Mode, UFT may replace test objects with XPath or CSS identifier property values with new objects from your application.
Workaround: Use the Update from Application option in the Object Repository Manager to update specific test objects with XPath or CSS identifier property values.
|Objects used in function library||Maintenance Mode cannot fix problems in an object's properties, if the object is used in function library that is called by a step. If Maintenance Mode detects a problem in an object in a function library, a message is displayed indicating that the test is read-only and that Maintenance Mode is disabled.|
The Update Run mode does not update Insight test objects.
To update an Insight test object, open the object in the object repository, and click the Change Test Object Image button in the Test object image area.
|Checkpoints and output values||
Update Run does not support updating complex checkpoint and output value types such as File and XML.
During the Update Run, these checkpoints and output values run as they would in a regular run session and will fail if there are differences between expected and actual values.