You can now spy, record, and run tests on SAP applications that are based on SAP UI5 Web Components.

For details on testing SAP web-based applications, see Web-based SAP support.

You can now train the ABBYY OCR engine to identify unusual or unclear characters in your application.

If you already have a trained pattern, you can also use automation scripts to specify the trained pattern file to use for text recognition.

For details, see ABBYY OCR Pattern Training and the App.Options.PatternFileLocation property in the UFT One Automation Object Model Reference.

Some rich editor controls, previously identified as plain WinObject test objects, are now identified as WinEditor test objects. This lets you perform text editing operations on the rich editor controls used, for example, in Notepad, Windows 11 and Microsoft Outlook.

In addition, the WinEditor test object now supports a Set method, which lets you enter single- and multi-line text values in the editor.

For details, see the WinEditor test object in the Object Model Reference for GUI Testing.

This version includes a new AI Object Model, with improved AI-based object identification. This model is also available on the AppDelivery Marketplace.

To update the local AI Object Model on machines using earlier versions of OpenText Functional Testing, see Update local AI Object Models.

You can now use the SetText and SetSecureText methods on AIObjects when testing native mobile apps. For details, see AI-based Testing in the Object Model Reference for GUI Testing.

The following methods and functionalities are now supported for AI-based testing on Headless Chrome:

Automatic scrolling, Hover, ScrollOnObject, Scroll, DoubleClick, RightClick, LongClick.

For details, see AI-based Testing in the Object Model Reference for GUI Testing.

Now that these methods are supported, features that were available as a technical preview are now officially supported: 

• Running web and AI-based web tests in a Windows Docker container.

  For details, see Run web and AI-based web tests in a Windows Docker container.

• Running AI-based web tests on Headless Chrome, including methods that were not supported previously.

  For details, see AI-based testing.

You can now retrieve and check the color and background color of text on a terminal emulator monitor.

Use the TeField.Color and TeField.BackgroundColor properties, described in the Object Model Reference for GUI Testing.

When running tests on a terminal emulator using VT emulation, you can now simulate pressing the numpad keys, as opposed to the number keys in the keyboard area.

For details, see the TeTextScreen.Type method in the Object Model Reference for GUI Testing.

Installation now requires .NET 8.0.6 Desktop Runtime.

If this version of the prerequisite is not installed before you install OpenText Functional Testing:

• Installing the full package installs the prerequisite automatically as well.

• When using silent installation, install the prerequisite as described in Silent commands for installing prerequisites.

The AI Object Detection feature is no longer a prerequisite for installing the OpenText Functional Testing for Developers.

• Using the installation wizard, you can install the OpenText Functional Testing for Developers feature without installing the AI Object Detection feature. For details on selecting features for installation, see Custom Setup screen.

• When installing silently, to include the AI Object Detection feature, you need to specify it explicitly. It's not installed automatically when you include the OpenText Functional Testing for Developers feature. For details on silent installation, see Include specific features.

You can now instruct silent installation to automatically enable the Chrome or Edge browser extension after installing it.

This can facilitate automated enterprise installation, as it does not require manual intervention to enable browser extensions.

For details on the new options for controlling browser extension installation, see Set configuration options.

You can now connect to the license server using a proxy.

In the Functional Testing License Wizard, select Concurrent license or Commuter license, click Proxy Settings and enter the proxy connection details.

You can use the System proxy or an HTTP proxy, and specify credentials for proxy authentication, if needed.

For details, see Manage licenses with the wizard.

In Java SWT GUI tests, extended ASCII codes are now supported when running Type and Set methods. For example, this enables tests to type strings with Umlauts in German.

For details on typing in Java Edit boxes, see the Object Model Reference for GUI Testing.