Release notes

Comparing the equivalence of PDF files and texts

We are excited to announce the ability to effortlessly compare PDF files and various text pieces using designated comparison types and rules. You can choose to compare documents and texts based on lines, characters, or words. Additionally, you have the option to establish custom rules, employing either regular expressions or wildcard syntax, for the purpose of excluding specific content segments from the comparison process.

To increase flexibility in your automation projects, the ability to compare documents and texts is available for both low-code and coded automations. Refer to the following resources to understand how to use Testing activities and APIs in comparing documents and texts:

Added 2 July 2024: Fixed the behavior of the Get Test Data Queue Item activity which did not return more than 1000 queue items.

New Verify APIs

To help you automate more of your testing process, we've added new APIs for verifying your testing scenarios. Check the following table showing the new APIs that you can use:

New or updated overloads for the existent Verify APIs

To simplify your testing efforts, we've added new overloads for the VerifyExpression, VerifyExpressionWithOperator, and VerifyRange APIs. The following table displays the API and their new or updated overloads.

Fixed an error that occurred when editing a read-only file for test auto-generation. The solution was to add a Finally block in the Test with Timeout template.

Testing APIs

If you prefer to code when building automations, you can now achieve this using coded automations and UiPath services! You can create coded automations using the UiPath services such as Testing.Activities, offering you APIs to use in your automation projects.

Visit the Testing APIs section to browse through the available APIs and Coded Automations Introduction to learn how to create coded automations.

Introduced enhancements to offer a more powerful user experience.

The Testing.Activities user interface is now available in Traditional Chinese.

Introduced enhancements to offer a more powerful user experience.

After you migrated your projects from Windows - Legacy to Windows, you couldn’t interact with the following activities:

The Output field inside the Random Date activity was non-interactive for Windows and cross-platform projects.

The Testing activities user interface is now available in Traditional Chinese.

You can now use the Verify Range activity to test expressions in a given range, so you can have more control over attributes in your testing worflows.

Fixed an issue in which verification activities failed when testing long running workflows. This issue was caused by a failed refresh token request.

Opening a Robotic Enterprise Framework template in Studio version 2021.10.4 resulted in an error. This issue occurred in scenarios where all online feeds were disabled and the installation package folder was deleted.

Resolved a regression with Verification activities throwing an exception when executed in an Orchestrator RPA Process.

An issue affected workflows with mocked activities. Removing a connection between a starting node and an activity that was surrounded with Mock, then establishing a connection to a new activity caused the Mock file to be discarded.

Running a workflow containing attached documents while connected to Orchestrator, threw an exception error. This issue has been addressed by skipping the activity at Studio runtime.

A difference in the library version of a dependency shared by the Testing and WebApi packages resulted in HTTP Request errors. This issue has been addressed by removing the library from the Testing package.

New Rules

The following Application Testing Workflow Analyzer Rules are available so you can maintain the same level of automation for projects that have multiple stakeholders:

The Verify Expression, Verify Control Attribute and Verify Expression with Operator activities have new properties that add additional capabilities:

An issue affected assertion posting to Orchestrator (v2020.4). If the Robot did not have permission to upload the assertion the workflow continued to run without returning an error.

You can now create synthetic test data to support your testing efforts. For example, this comes in handy when production data cannot be used for testing purposes, due to data regulations such as GDPR. Creating your artificial data provides high coverage and is easy to reproduce, as opposed to copying or anonymizing existing production data.

To learn how to create synthetic test data, see the following new activities:

The first iteration of the Testing activities pack offers three activities designed to enable verification of logical expressions and control attributes in your testing workflows. The new activities are: