You can now perform a business flow on your application and create a sequence of AI steps in your test. Within the recording session, you can also fine-tune the object identification and add checkpoint steps.

See Record an AI-based test.

Learn AI objects on application mockups and prepare your AI-based tests before your application is developed.

See Inspect application mockups for objects.

Run your existing tests with the AI Transformation Assistant enabled, to receive suggestions for transforming technology-based test steps to AI-based testing steps. Replace existing steps with the suggested AI object steps to create a more resilient and platform-agnostic test.

To enable the assistant in Tools > Options > GUI Testing > AI, select Replace run results with AI step suggestions. See Convert technology-based tests to AI-based tests.

When running a test, if the object is not displayed in the application but the web page or mobile app is scrollable, UFT One automatically scrolls further in search of the object.

You can configure the direction of the scroll and the maximum number of scrolls to perform, or turn off scrolling if necessary. For more details, see Automatic scrolling.

AIObject and AITextObject now support checkpoints! You specify the condition the application must meet to pass the checkpoint, and if expectations are not met, the step fails, which is reflected in the run results.

• CheckExists checks the existence or absence of an object in your application.
• CheckState checks the state of objects that can be set to Off or On, such as checkboxes, toggles, or radio buttons.

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

You can use any of the following options to optimize text recognition when using AI-based testing features:

• Recognize text in multiple languages.

  Supported languages: English (default), French, German, Italian, Japanese, Russian, Simplified Chinese, Spanish.

  Configure the languages to expect to find in your application (Tools > Options > GUI Testing > AI).

• Temporarily request exact text matching instead of AI algorithms, which find similar text.

  AI text matching may consider spelling variations and words with similar meaning to be matches. If necessary, you can instruct UFT One to look exactly for the specified text when identifying AI test objects.

  Add an AI run settings step to your test to set the text matching method. The setting is effective until you change it or until the end of the test run. For details, see the AIRunSettings Object in the Object Model Reference for GUI Testing.

• Instruct AI to use the UFT One text recognition settings. Depending on your configuration, this enables you to use Google or Baidu OCR cloud services or other OCR engines.

AIText objects support new methods:

• Use the new GetText method to retrieve text from AIText objects.

  For example, identify an AIText object with unknown text by its proximity to another object. Then retrieve its text using GetText.

  Note: The constant that specifies text should be ignored when identifying a text object by location has been renamed. If any of your existing tests used the micNoText constant, replace this with micAnyText to prevent your test from failing.

• Use the Type and TypeSecure methods to type in input or edit boxes that you could only identify as AIText objects.

See the AIText Object section of the Object Model Reference for GUI Testing.

To support a control that UFT One AI does not recognize, provide an image file as a class description.

For details, see Describe a control using an image.

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

• New control types and type names are now supported:

  On web and mobile apps: check_mark, minus.

  On web applications only: Linkedin, Instagram, rss_feed.

• Use general names to include multiple control types:

  left for left arrows and left triangles. Similarly, you can use right, up, and down.

  Toggleable or Togglable for controls like toggle button, checkbox, and radio button.

  field for controls that accept text, like text boxes, inputs, and combo boxes.

When a GUI test that is run by ParallelRunner calls an API test, the API test now runs correctly. The results of the API test are displayed together with the rest of the parallel run results.

This version uses an updated version of log4net.dll.

If your API tests were created and built 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 the custom activities were created by earlier Activity Wizard versions, you must recompile those activities with the log4net.dll from the <Unified Functional Testing installation>/bin folder before you can use them in your API tests. For details, see Known issues- Custom API testing activities.

Significantly reduce test execution times compared to previous versions.

In the following browsers, objects are now correctly identified even if your web page is zoomed in or out: Chrome, Chromium Edge, Firefox.

Automatic page checkpoints are now supported for Firefox or Chrome browsers. See Web > Advanced Pane (Options Dialog Box).

Activate web testing acceleration by selecting the option in Tools > Options > GUI Testing > Web. This option is offered as a technical preview.

The acceleration option speeds up test runs for half of the web test object types. For details, see Accelerate web testing on Chrome, Edge, and Firefox.

In the following browsers, objects are now correctly identified even if your web page is zoomed in or out: Chrome, Chromium Edge, Firefox, IOS UFTM Browser, IOS Safari.

When recording and running tests on packaged Android and iOS apps built using the Google Flutter SDK, UFT One now identifies object types and interacts with the objects accordingly.

The following test objects are supported: MobileButton, MobileCheckBox, MobileEdit, MobileLabel, MobileObject,MobileTabStrip.

For details on the supported Flutter SDK version, and guidelines for preparing and uploading Flutter apps see the Digital Lab Help Center.

In the Record & Run settings, you can now select the following device metrics: 

WiFi state, thermal state, and available disk space.

Respectively, the run results include new metrics: WiFi signal strength, thermal state, and available disk space.

The new version of the Jenkins plugin provides the following capabilities:

• You can now define ALM credentials globally in your Jenkins server instead of defining them separately in each job.

  We provide a utility that you can use to migrate existing credential into the global Jenkins settings. However, existing jobs can still using previously defined credentials. For details, see Define ALM credentials on the Jenkins server.

• The Jenkins plugin options for rerunning failed tests were renamed, and also include a new option for rerunning all failed tests. For details, see Configure failure scenarios for your test runsTesting with Jenkins

The new version of the UFT One Azure DevOps extension includes a task execution handler update, bug fixes, and the following functionality.

When running tests on an Azure DevOps Server, you can now view the UFT Report with test run result details on the Azure DevOps Server, in the Extensions tab.

• You can now pass input parameters to UFT One tests when you run them from a Bamboo server.

  Create an .mtbx file that provides the parameter values to use for each test.

• The suffix of the JUnit report is now based on the Bamboo system variable bamboo.buildTimeStamp. This enables you to refer to it automatically in a script or job and import it to an external system.

Function libraries saved as .qfl or .txt files, are now saved in UTF-8 encoding. This enables you to compare, merge, and manage them in GIT. Function libraries saved as .vbs files, can be managed in GIT only as binary resources.

Web-based SAP applications are now fully supported when working in a Chrome browser. Support is now available for the following test object types, in addition to the ones supported in the previous version.

• SAPCalendar

• SAPNavigationBar

• SAPNWBC
• SAPPortal
• SAPTable
• SAPTabStrip
• SAPTreeView

Note: Testing SAPUI5 Desktop applications and SAP Business Networks Web applications continue to be supported on Chrome, as they have in previous versions.

SAPUI5 test objects are now supported when working with Chromium Edge.

Use this new method to more simply retrieve the values contained in a specific area of a Java table.

See the JavaTable topic in the Object Model Reference for GUI Testing.

Scroll bar controls in JavaFX applications are now supported.

They are identified as Slider test objects (is_scrollbar property = 1), similarly to AWT and Swing applications.

A new light-weight UFT One Docker image is now available on Docker Hub. The uft-lite image provides the same functionality as the full image, but is much smaller and faster to download. See Run tests in a Docker container.

Spy, record, and run tests on the following DevExpress grid controls using the .NET Windows Forms Add-in:

• Data Grid
• Pivot Grid
• Vertical Grid

These grid controls are all identified as SwfTable test objects. Each type supports a different set of methods. For details, see the SwfTable topic in the Object Model Reference for GUI Testing.

You can now use the SetActiveAddins method in a UFT One automation script even after calling the Launch method to open UFT One.

The set of add-ins you specify replaces any currently loaded add-ins.