What's new in 25.3

You can now check the value of an input or output parameter in Verify and Smart Verify steps, and in plain If statements.

For details, see Add verification steps and Add conditional steps.

You can now add steps that operate on the browser itself: Refresh application, Clear browser cache, and Delete cookies.

For details, see Step syntax.

In your Design script, you can now add calls to JavaScript functions, which can perform operations that are not possible in the codeless scripts. For example, functions can retrieve multiple values and perform mathematical operations on those values.

Develop your functions using JavaScript as well as AI and Web functions from the OpenText Functional Testing for Developers JavaScript SDK.

For details, see Custom functions.

The Design Agent installation includes a new version of the browser extension used to test web applications. The extension was renamed to OpenText Functional Testing Agent and upgraded to version 2025.2.x.

To use the new browser extension, follow the instructions in Set up the browser extension.

Automated Run and Suite Run entities now include the Aviator Smart Assistant pane. Aviator can analyze your automated test run results, provide failure analysis, suggest potential fixes, and report on historical runs and trends.

For details, see Analyze test run results with Aviator.

Note: This feature requires an Aviator license.

When you generate a Model using Aviator, you can now create additional drafts of the suggested Model, fine-tuning your feature description and improving the Model generation.

For details, see Generate a model with Aviator.

Note: This feature requires an Aviator license.

When you generate a Model using Aviator, the Model's placeholders now include descriptions and expected results, rather than just a name.

You can subsequently convert one or all placeholders to units, which also contain those descriptions.

For details, see Generate a model with Aviator.

Note: This feature requires an Aviator license.

You can now add Termination endpoints to your Model-Based Testing models. A Terminate point represents a point in the business process where the flow should immediately terminate.

This is useful when you don't want the flow to continue in a parent model after the child model ends.

For details, see Build and edit a model.