Known Issues - UI Automation Support
Working with UFT One and UI Automation has the following known issues:
The following features are not supported together with UI Automation:
Tests created in previous versions of UFT One
Some tests created on previous UFT One version may fail when running the test, 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 One to find the object more quickly during test runs.
Testing the ALM Client application using UFT One with UI Automation is not supported.
UI Automation recording and UI Automation spy mode can experience unexpected behavior when running UFT One on Windows 10.
These functionalities are not officially supported for UFT One running on Windows 10.
If you are using UI Automation to record in an environment with a slow GUI refresh such as a slow RDP connection, recording can experience unexpected and unstable behavior.
Additionally, recording on UI Automation Add-in test objects may not identify all objects due to a page refresh. To avoid errors, add any relevant steps manually in the Editor.
|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 One 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 One experiences unexpected behavior.
Navigate and learn is not supported for capturing objects nested within other objects.