What's new in 25.2

You can now specify a rule or regular expression for an object's identification text.

This helps identify objects by text which can change, such as price, count, or ID.

For example, you could write steps like these: 

• Click the Button whose name ends with "Total"

• Click the Button whose name matches "\w+\s\d+\,\s\d+"

• Verify that the value of the input whose name contains "Total" contains "$49.99"

For details, see Use rules and regular expressions.

When running a script in Design, you can select to run it on an application that is already open.

This enables you to run a script on an application in its current state, rather than having to start from the application’s initial state when launched.

This is helpful when running a succession of scripts where the first script opens the application and the others start from a later stage in the business flow. For example, if you run the scripts of units that comprise an MBT test and do not each open an application.

For details, see (Optional) Configure script applications.

You can now control the flow of your script based on the value of an object by checking the value in an If statement.

You can verify whether the value is empty or not, and whether it is or isn't equal, containing, or within a specified string. The string you specify can be a parameter or a constant.

Previously, condition steps could check only for an object’s existence.

For details, see Add conditional steps.

When editing a script, you can now edit an object's related objects in the step editing pane.

Previously, such editing was possible only when adding the relation, which is done during inspection.

Editing related objects in the step editing pane also enables you to use the Partial text option for related text objects.

For details, see Manually edit steps.

In Smart Verify steps, when you type '@' to use a parameter, you can now select an existing parameter from the list or create a new script parameter.

For details, see Add verification steps.

Note: This feature requires an Aviator license.

Leverage Aviator’s Generative AI capabilities to automate your Model by automatically generating codeless scripts from your units' manual tests.

For details, see To generate a codeless script from a linked manual test.

Note: This feature requires an Aviator license.

When running OpenText Functional Testing tests on the cloud, the test runs are recorded as .MP4 video files. You can then download the recording.

• Use these videos for improved debugging and visual verification.

• Share these recordings for better collaboration and insights.

For details, see View detailed run results.