Known Issues - UI Automation Support
The following features are not supported together with UI Automation:
|Tests created on previous UFT versions||
Some tests created on previous UFT version may fail when running the test. This is due to an update in the description properties used to identify objects.
Workaround: Check the test object's name in both the Object Spy and the Object Repository. If necessary, update the Object Repository to match the value of the name property in the Object Spy.
Tip: Always use the name property for object identification in UI Automation objects. This property enables UFT to find the object more quickly during test runs.
|UI Automation on Windows 10||UI Automation recording and UI Automation spy mode can experience unexpected behavior when running UFT on Windows 10. (Note that these functionalities are not officially supported for UFT running on Windows 10.)|
|Recording on environments with slow GUI refresh||If you are using UI Automation to recordin an environment with a slow GUI refresh such as a slow RDP connection, recording can experience unexpected and unstable behavior.|
|UI Automation and Java applications||
When using UI Automation to test a Java application, objects added to your object repository from an application running on a computer with Java 8 installed will not be recognized on a computer with Java 6 installed.
This is due to changes in the Java framework between Java 6 and Java 8.
|Regular expressions as property values||
The controltype cannot have a value that is a regular expression.
|UIA container objects with large numbers of elements||
When spying on UIA container objects, such as lists, trees, and tables with large numbers of elements in the object, UFT may experience slow performance and unexpected behavior.
Workaround: Do one or more of the following:
|UIA with other "spy" tools||If you start other "spy" tools, such as the Microsoft Inspect tool, UFT experiences unexpected behavior.|