The following features are not supported together with UI Automation:

• Active Screen

• F1 support for objects and methods

• Table checkpoints

• Recording on Drag and Drop methods.

Tests created in previous versions of OpenText Functional Testing

Some tests created on previous OpenText Functional Testing 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 OpenText Functional Testing to find the object more quickly during test runs.

Testing the ALM Client application using OpenText Functional Testing with UI Automation is not supported.

UI Automation recording and UI Automation spy mode can experience inconsistent behavior when running OpenText Functional Testing on Windows 10 and later.

These functionalities are not officially supported for OpenText Functional Testing running on Windows 10 and later.

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.

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, OpenText Functional Testing may experience slow performance and unexpected behavior.

Workaround: Do one or more of the following:

• In your application, implement the ItemContainer pattern with the FindItemByProperty() method.

• Manually add additional description properties for the items in the object, such as index. These properties are not added by default.

• Use .Object methods to access items within the control.

If you start other "spy" tools, such as the Microsoft Inspect tool, OpenText Functional Testing experiences unexpected behavior.

Navigate and learn is not supported for capturing objects nested within other objects.

When testing Excel documents using UI Automation, the following issues are known:

• Recording or running test steps on certain controls generates errors

• Text recognition is inconsistent

• UIAEdit does not support the SetSecure method

• Screen captures are not available in the Run Result Viewer

• In some cases, controls spied using UIA cannot be highlighted or added to an object repository

• Performance is low