Install the Remote AI service on one central powerful computer, to provide faster and more efficient AI capabilities to less powerful UFT One machines.

For details, see Use the remote AI Object-Detection service.

UFT One's AI Features incorporate AI models to assist AI-based testing. When a new model is available, you can update to the new model to improve test performance and accuracy.

You can update your AI model from the UFT One user interface, or run the ModelInstallApp.exe command in the command line tool. For details, see Improve AI-based test object identification.

Object identification verification increases test run success rate and test resilience:

Before performing an operation, the object identification is verified to make sure the object has not changed.

By default, verification is enabled for non-mobile contexts and disabled for mobile contexts. You can change the context settings or disable identification verification. For details, see Verify object identification.

AIUtil and AI objects now support the following functionalities: 

• AIUtil.Context.SetBrowserScope lets you specify whether to inspect the whole browser for objects. This is useful when your test needs to respond to a browser's pop-up dialog box.

• AIObject and AITextObject now support a GetValue method, which retrieves the object’s value.

• AIUtil.Scroll and AIUtil.ScrollOnObject let you scroll your application, from the middle of the page or screen, or from a point over a specific object.

See the AI-based testing section of the Object Model Reference for GUI Testing.

Use a new combined and consistent interface to inspect both live applications and application mockup images.

When working with live applications, you can now do the following:

• Select your application and add a corresponding SetContext statement to the test.

• Extend the inspection to the full browser window and add a corresponding SetBrowserScope statement to the test.

• Bring the application you are testing to the foreground with a click of a button.

• Delay the inspection by a few seconds, allowing you to interact with the application before it's inspected for objects.

• Run the step you add to the test. This helps bring the application to the next state so you can re-inspect the application and design the next step.

AI-based testing can now recognize text in more than forty languages.

For a full list of supported languages, see Configure OCR settings.

New control types and type names are now supported:

• On mobile apps: power, filter, exit, lock, sort, upload.

• On web applications: power, up_arrow, up_down, YouTube.

For a full list of supported controls types, see AI-based testing: Supported control types.

The following changes may require adjustments to existing tests:

• The up alias now represents both up arrows and up triangles. Previously it was used only for up triangles.

• The single-word aliases arrow and triangle have been discontinued. Class names such as left_arrow and right_triangle are still supported.

Container objects

Tech preview

Using an object hierarchy can improve your test's readability and resilience.

Table and calendar controls can now be seen as containers or parent objects.

See the AI-based testing section of the Object Model Reference for GUI Testing.

This version provides the following mechanisms to improve the performance of AI-based testing:

• To improve AI-based testing performance, OpenText Functional Testing uses a caching mechanism for object identification during the test run. You can disable the caching in the AI pane in the Options dialog box. See AI Object Detection Pane (Options Dialog Box > GUI Testing Tab).

• Use the new AIUtil.Context.Freeze and UnFreeze methods to prevent the application from being reinspected between steps, if you know the application is not expected to change.

You can now run tests on web applications in Chromium Edge when using IE mode.

Spying and recording are not supported in IE mode.

Web testing acceleration is now officially supported and enabled by default. This speeds up test runs for most web test objects and methods. 

For details, see Accelerate web testing on Chrome, Edge, and Firefox.

When working with the Safari browser, additional functionality is now supported:

• Test web applications on multiple tabs.

  The Browser.OpenNewTab method opens a new tab and navigates to the URL for new tab, defined in the Safari extension's settings. For details, see Install and configure the OpenText UFT Agent Safari extension on Mac.

• Use the CaptureBitmap method to take screen captures of your application objects during the test.
• Highlight objects from the object repository in your application.

To open your PDF document in order to run a test on it, do one of the following:

• In OpenText Functional Testing, using the PDF Testing Utility button or menu command (in the Tools menu). See PDF Add-in.

• In your test, use a PDFUtil.Open statement.

Running PDF tests created in previous versions

To run tests created in previous versions of UFT One, do the following:

1. Change your tests to open the PDF document using the PDF Testing Utility, as described above.

2. Run your test in maintenance mode to update the properties that OpenText Functional Testing uses to identify the objects in the PDF document. For details, see Maintenance Run mode.

(tech preview)

You can now run Java tests in parallel, using the Parallel Runner. You can also synchronize the test runs, so that certain tests run only after other ones passed or failed.

This functionality joins the existing capability to run web, mobile, and API tests. See Run tests in parallel.

A new version of the UFT One Azure DevOps extension is available. For details on using the new extension, see UFT One Azure DevOps extension updates .

The new extension provides some UI updates, as well as the following enhancements: 

• When running tests from the file system, you can now do the following:

  • Choose to generate a detailed run results report for each test run, without the need to add a Publish Test Results step to your pipeline. For details, see View the test results.

  • Upload the test results generated by UFT One to an Azure Storage account. This lets you access the results from the Azure DevOps Server. For details, see Set up Azure Storage for your OpenText Functional Testing test results.

• When running tests from ALM Lab Management, tests now run on the hosts configured in the ALM Lab Management setup.

• When running tests from ALM, configure the report names to use the pipeline name and build number environment variables. This helps retrieve the reports in Azure DevOps. See Run a test saved in ALM.

You can now connect to an ALM server that requires SSO authentication. In your Bamboo task, instead of a user name and password, enter the Client ID and API Key secret you received from the ALM site administrator.

API tests can now refer to external data tables by relative paths, not only absolute paths. This makes it easier to work with tests and data tables stored in a SCM system and checked out to different locations for running.

UFT One CI Utilities

This version introduces a set of utility tools on GitHub for users who are using a CI-CD server. With this set of tools, you can easily integrate UFT One into your CI-CD pipeline without plugins and implement the following activities using CLI commands:

• Run multiple types of UFT tests, and generate a summary report for each test run.

• View test execution status in runtime, and convert HTML test reports into JUnit XML format.

For details, see UFT One CI Utilities on GitHub (select the readme file for the latest release).

For details, see Available OpenText Functional Testing Docker images.

The Object Identification Center includes the following updates:

• You can view the native properties, native operations, and test operations of an object in an open application.

• OIC's Validate functionality now works on all technologies, including mobile, UIA, Java, Oracle, and SAPGUI.

Use JSON file content in your GUI tests

UFT One can now read data from a JSON file using the Parse method. You can store test input data in a JSON file and run a single test script for all the test data in the file.

For details, see Use data from JSON files in GUI tests.

SAP Secure Network Communications (SNC)

UFT One now supports connecting to Solution Manager servers with user/password authentication using Secure Network Communications (SNC).

For more information, see Solution Manager Connection dialog box.

You can now test the API functionality of your Kafka server. Kafka activities in Toolbox > Standard Activities enables you to verify the processes of publishing messages to topics, or receiving and deleting messages from your Kafka server.

For details, see Test with Kafka activities.

API tests now use the new data table, which supports Excel's .xlsx format and provides faster response times.

The new data table features many enhancements:

• Support Excel's new formulas and functions.

• Maximum cell content length extended from 16K to 32K characters.

• Maximum number of columns extended from 256 to 16K.

• Jump to a specific cell in the data table by entering its coordinates (for example G27) in the box in the top left corner of the pane.

The new data table includes some user interface updates in the test's Data Pane. For example, the parameter names display in the first row of the table instead of in the column headers.

You can now store the location of a local excel data source added to an API test, using a relative path.

This is useful when you have multiple servers checking out the same tests from a Content Management System (CMS) to different UFT One machines.

A newer version of log4net.dll is now being used.

If your API tests were created in earlier UFT One versions, to continue to use your tests, you must upgrade them by opening them in a new version of UFT One.

If custom activities were created by earlier Activity Wizard versions, you must recompile those activities with the log4net.dll from the <Installdir>/bin folder before you can use them in your API tests. For details, see Known issues- Custom API testing activities.

Preview text recognition results while you configure your text recognition settings. This helps you reach the optimal setup for your needs. To open the Preview pane, go to Tools > Options > GUI Testing tab > Text Recognition node > Preview button.

The preview result can help you optimize your settings. You can adjust your settings globally in the Options Window, or locally in your test for a specific test run.

For details, see Preview Pane (Options Dialog Box > GUI Testing Tab > Text Recognition) and Verify the text recognition configuration.

You can use the SetABBYYParameters method to specify ABBYY parameters and optimize your ABBYY OCR mechanism for a specific test run.

Available ABBYY parameters are displayed in the Preview pane and you can use the Generate/Copy Script button to generate TextUtil.SetABBYYParameters steps and add them to your test.

Tesseract version 4.1.1 is now used for the Tesseract OCR engine.

The new updated Tesseract version provides more precise optical character recognition.

Note:

• This change may affect the text recognition behavior in your existing tests.

• If you were using Tesseract OCR for non-default languages, you need to download the updated language packs for this version. See Current language pack in the Configure text recognition settings topic.

APITest objects are available in the AOM, enabling the following capabilities:

• Add a call to an existing API test from the current action or GUI test. Use the AddExistingAPITest method in the Test or Action object. See the Action Object or the Test Object in the UFT One Automation Object Model Reference.

• View the total number of API tests and retrieve the path of a specific API test in an API test collection. See the APITests collection in the UFT One Automation Object Model Reference.

• View the name or path of an API test. See the APITest object in the UFT One Automation Object Model Reference.

Add a call to an existing action in the current action or test.

Use the new AddExistingAction method in the Test or Action object. See the Action Object or the Test Object in the UFT One Automation Object Model Reference.

The following processes now take less time: 

• Opening UFT One

• Opening tests

• Working with the remote access window to access your mobile applications.

Do one of the following to open a test:

• Right-click the test file folder or the test file and click Open in UFT in the context menu

• Double-click the test file

Add a test to an open solution by dragging and dropping the test file folder into the Solution Explorer.

Add a Text test object by using the Add Text Object button on the record toolbar when recording a business component. See Record a Text object step.

Rebranding continues, file locations updated

The new company and product name now affect file locations as well:

• The configuration files are now stored in Micro Focus folders.

  The first time you run UFT One 2021, any existing setting files are automatically migrated to the new locations. This enables you to continue using your existing UFT One settings in the new version. For details, see Configuration file location.

• The default folder for saving new tests is now My Documents\UFT One. Tests created in previous versions and stored elsewhere, are not automatically moved. You can continue to use them from their original locations.

Upgraded infrastructure

The Chromium Embedded Framework (CEF) is now used for the UFT Mobile remote access window, to improve performance and functionality.

Microsoft Visual C++ 2019 Redistributable - a newer version of this redistributable is now being used.

.NET 5.0.6 - To work with new UIA Pro add-in or the Parallel Runner UI, you must have .NET 5.0.6 installed. When you install the full UFT One package, this prerequisite is installed automatically.

If you use silent installation or you install the lighter UFT One installation, make sure to include these prerequisites when you install.

The SAPWDJ Add-in has been discontinued. If you open tests associated with this Add-in, you will encounter a warning message that this add-in is associated with the test but not installed.

Deselect this add-in in the test’s settings, and if needed, adjust your test to use the Web Add-in for the SAPWDJ objects.

Angular

10*, 11*, 12

11.7.0*, 11.8.0, 11.9.0, 12.0.0

20.2

14

Java

• Oracle Java SE 16

• OpenJDK 8, 9, 10, 12, 13, 15, 16

• Zulu OpenJDK 14*, 15, 16

For version 16, follow the configuration requirements in Java environment variables.

2019, 365 (using the UIA Add-in)

• E-Business Suite 12.2.10

• Oracle applications supported with Java 64-bit versions

8.1 (32 & 64 bit)

• SAP Fiori 1.84

• SAP GUI 7.60 up to patch 12

• SAP GUI 7.70 up to patch 3

• SAP NWBC 7.0 up to patch 21

• SAP NWBC 7.7 up to patch 6

• SAP SuccessFactors

We recommend working with the latest supported patches. For known issues when working with earlier patches, see Known Issues - Windows-based SAP.

87-92

87-92

83-91, 91 ESR