2025 Release Notes
This release notes documentation contains package updates and the list of new features and fixed issues for all Test Automation releases in 2025.
For the most recent product highlights, see What’s New in Test Automation.
Test Automation 3.5.0
Release Date: 30 Sept 2025
New Features
This section provides the list of new features and enhancements that have been added in this release.
| Affected Module | Description |
|---|---|
| Assertion | APIs to check and delete assertions have been created. |
| Assertion | Assertions can now be deleted in the Assertion module. If a dataset is used in a flow, it will not be deleted. Instead, a list of all flows using the dataset will be displayed. |
| Assertion Dataset |
Assertions associated with a dataset cannot be deleted in the Dataset module. |
| Dataset | An assertion can now be enabled or disabled in the Dataset module. If an assertion is disabled, details cannot be viewed or modified. |
| Dataset | Flows using out-of-sync datasets are now prevented from being executed. |
| Dataset Flow |
Out-of-sync datasets can now be synced. |
| Flow | Test flows can now be deleted in the Flow module. When a test flow is deleted, all associated datasets will also be deleted. |
| Flow | Test flows can now be imported from an exported flow file. |
| Flow | Test flows can now be exported to a JSON file. |
| Flow | Assertions can now be generated with an AI module. |
| Flow | Multiple AI-generated assertions can now be merged into a single assertion. Also, an assertion can be unmerged to retrieve the individual assertions. |
| Flow | AI-generated assertions can now be edited before applying them to the step. |
| Flow | A timeout can now be specified to define how long a step should wait for a response before marking it as failed. |
| Flow | The Parent Step Request and Parent Step Response node types are now supported in assertion inputs and expected fields. |
| Flow | An Import API is now available to process the export file created by the Export API. |
| Flow | An export API is now available to create an export file containing test flow components. |
| Flow Project |
The icons in the version form have been replaced with Cancel and Save buttons. |
| Flow Project |
Modal actions are now aligned properly. |
| Flow Project |
All details in the side form are now visible even after resizing it. |
| Flow Scenario Step |
Character limit for Step Description and Scenario Description fields are now 1000. |
| Flow Settings |
[FE] Migrate Large Feature Module from RDS → PDS — Plan |
| Project | An API to delete a project and all its associated entities is now available in the Project module. |
| Project | An API to display the count of all associated entities is now available in the Project module. |
| Project | Projects can now be deleted in the Project module. If there are any associated entities, they will be displayed before the deletion is confirmed. |
| Run Result | Screenshots and reports are now stored in different folders for each step. |
| Settings | AI modules can now be integrated with TA. Configurations are handled in the Settings module. |
| Step | Steps can now be deleted in the Step module. If a step is used in a dataset, it will not be deleted. Instead, a list of all datasets using the step will be displayed. |
| Step | A value for UI step can now be configured as a file or a text. |
| Step | A step that has been deleted in a test flow now remains accessible in other project versions it was associated with. |
| Step Run Result |
Files are now displayed and can now be downloaded when viewing the unit test result of an Upload UI step. |
Fixed Issues
This section provides the list of issues that have been fixed in this release.
| Affected Module | Description |
|---|---|
| Assertion | The Send button is now enabled when all required fields have been populated. |
| Assertion | Fixed an issue where the Request Body field is emptied when saving an assertion. |
| Assertion Flow Step |
Query and path parameters can now be configured for API steps in the Assertion and Flow modules. |
| Authentication | Fixed an issue where ORMB environments requiring only a single-step authentication (ORMB Authorization API) were incorrectly following a two-step process, resulting in authentication failures in services such as the load batches API. |
| Dataset | Fixed an issue where missing values in required user fields of Excel dataset templates were replaced with NA instead of an error message. |
| Dataset | Fixed an issue where the template name from the first selected step was incorrectly applied to subsequent steps. |
| Dataset | The Save and Run buttons are now enabled when a dataset has been modified. |
| Dataset | The dataset is now displayed in the Results module during execution. |
| Dataset | The default version is now being captured by the Version field when creating a new dataset. |
| Dataset | The warning message for dataset configuration using the wrong version is now displayed properly. |
| Dataset | Fixed an issue where the step payload is not displayed during dataset creation when the version is being changed. |
| Dataset | Fixed an issue where the default value is being used instead of the new value configured for execution. |
| Dataset | The Integer data type is now accepted when uploading a bulk dataset. |
| Dataset | Fixed an issue where the page becomes unresponsive when clicking anything but the Save button during entity modification. |
| Dataset Flow |
Fixed an issue where subsequent steps are loading even if the first step is not yet completed. |
| Flow | Fixed an issue where a testflow with an associated dataset can be deleted. |
| Flow | Fixed an issue where the dataset template and steps are loading when viewing a test flow in a version where it was not created. |
| Flow | Fixed an issue where datasets not associated with the selected version are displayed when configuring a flow. |
| Flow | The response payloads are now displayed for queries executed in the Flow module during step linking. |
| Flow | Query steps created in the Flow module are now working as expected. |
| Flow | Fixed an issue where multiple executions were created when running a flow with multiple environments. |
| Flow | Fixed an issue where the Environment and Dataset details were hidden when the scenario name is long. |
| Flow | Fixed an issue where passing executions have failed steps. |
| Flow | Fixed an issue where an error was encountered when creating a test flow with a name that had already been deleted. |
| Flow | Fixed an issue where a deleted test flow was accessible by ID. |
| Flow Scenario |
Scenario description tooltip now displays the entire content, even if it has 1000 characters. |
| Flow Step |
Fixed an issue where payload attributes are not displayed even if the associated template has a step with attributes. |
| Flow Step |
Fixed an issue where a Query step fails in the Results module but passes in the Step module. |
| Flow Step |
Correct screenshots are now displayed for UI steps executed in the Flow module. |
| Flow Step |
The store command is now working properly. |
| Flow Step |
Fixed an issue where error messages are encountered when linking a variable from a Batch step to an assertion. |
| Report | The Executed For Project report field now correctly displays the project name. |
| Results | Fixed an issue where duplicate results entries are being displayed on the Details tab. |
| Results | The column texts on Assertion Results no longer overlap. |
| Results | Fixed an issue where the first variable with a value similar to other variables is displayed in the UI logs. |
| Results | Secret passwords are no longer displayed in the UI logs. |
| Results | Fixed an issue where a failed step attempting to download a non-existent file was not displayed in the Results page. |
| Results | A proper error message is now displayed when executing a test flow that has no assertion input fields. |
| Results | Fixed an issue where the assertions list is empty when one target validation is non-existent. |
| Results | Success and failure banners are now disappearing automatically. |
| Results | Failed UI steps now include screenshots. |
| Results | Fixed an issue where text values were displayed as hyperlinks. |
| Results | You can now use a Run Number filter in the Run Results module. |
| Run | The filters on the Run module are now functioning as expected when applied. |
| Step | Fixed an issue where the verifyElementPresent captures the step description as the Target. |
| Step | UI commands that are configured to have blank values capture the Target values. |
| Step | A space is now accepted as a valid character for headers of API steps. |
| Step | A PDF file can now be uploaded or downloaded for an SFTP step. |
| Step | The UI SIDE file from TA version 2.x.x can now be used in TA version 3.x.x. |
| Step | The Upload button is now displayed for all UI File Upload steps. |
| Step | Step response payloads are now correctly displayed for steps with customized names or queries executed in the Flow module. |
| Step | Fixed an issue where the Update button is disabled after updating the step name. |
| Step | Variables are now working properly in UI steps. |
| Step | Correct application URLs are now displayed in UI steps. |
| Step | The following commands are now available for use: do, repeatif, while, end, and store. |
| Step | Fixed an issue where the screen gets refreshed when executing the do command. |
| Step | Fixed an issue where the result is not consistent when running a UI step. |
| Step | Fixed an issue where nodes are not captured when creating a new UI step default template. |
| Step | Fixed an issue where error messages are encountered when loading schemas or executing flows that take more time than expected. |
| Step | Fixed an issue where a UI step gets stuck when an element is not found. |
| Step | Fixed an issue where the other commands are overwritten after saving modifications while the filter is applied. |
| Step | Fixed an issue where an unselected header was included during execution in the Step module. |
| Step | The No image error message has been replaced with NO IMAGE SELECTED. |
| UI | The application logo has been replaced with the updated one. |
Test Automation 3.4.0
Release Date: 16 July 2025
New Features
This section provides the list of new features and enhancements that have been added in this release.
| Affected module | Description | Dataset | A new versionID parameter has been added to the GET API response. |
Environment | You can now upload a .pem file when using SFTP details for your test environments. |
|---|---|
| Project | In the Integrations tab, you can now search for a project by entering a keyword or the full project name in the Project Name dropdown and then, select the corresponding project name. |
| Run Result | A copy icon allowing you to copy the JSON payload data has been added to the Results details popup window. |
| Run Result | Assertions in WARNING are now represented by light gray color in the WARNING has been removed as the section does not display content. |
| Step | The Beautify button has been replaced with a beautify icon and is repositioned near the scrollbars. |
| Test Flow | When syncing the Test Flow to TestRail, the Sync Test Flow to TestRail popup window now lists all the scenarios and steps to be synced. |
Fixed Issues
This section provides the list of issues that have been fixed in this release.
| Affected module | Description |
|---|---|
| Assertion | The Rest Catalogue button in the Assertion Module is now enabled and working properly. |
| Bulk Dataset | Bulk dataset can now be uploaded. |
| Dataset | Test flow execution in the Dataset module is now working properly. |
| Dataset | Fixed an issue where some fields are automatically left blank after saving a newly-created dataset. |
| Dataset | Fixed an issue where datasets cannot be saved after modifying the assertions. |
| Dataset | Dataset templates not created at the time during the step creation can now be selected when creating a new step. |
| Dataset | An option to disable assertions during test execution at the Dataset module has been added. |
| Dataset | Fixed an issue where a duplicate error message is displayed when creating a new and unique dataset. |
| Dataset | Correct datasets are now fetched when executing tests from the Dataset module. |
| Environment | The PassPhrase field in the SFTP details is now an optional field. | Project | Project variables can now be created. |
| Run Result | The View links for Payloads and Assertions results on the Results page are now working. |
| Run Result | Fixed an issue where batch logs are showing in the assertions associated with a Batch step type. |
| Run Result | Fixed an issue where the live execution was not displayed after deployment. |
| Run Result | Fixed an issue where execution runs into an error when using Ocular authentication. |
| Run Result | Fixed an issue where the status of multiple dataset executions displays in progress when it was already completed. | Run Result | Fixed an issue where the execution status displays completed when no dataset was executed during multiple dataset executions. |
| Run Result | The Start a run button in the Results module is now working. |
| Run Result | Fixed an issue where the first step in running a flow results in an internal server error. |
| Run Result | Fixed an issue where the configured API Base URL is displayed when viewing an SFTP upload or download step. |
| Run Result | Fixed an issue where the scenario displayed on the Run screen is not the same with the order configured in the test flow. |
| Run Result | Query step with query assertion is now working properly. |
| Run Result | Batch execution is now working properly. |
| Run Result | SFTP file upload reports can now be downloaded. |
| Run Result | The spacing between the assertion name and status is now displayed properly on the Assertion Run Result page. |
| Run Result | Fixed an issue where a variable value is not displayed in the UI log when the same value was set for a secret variable. |
| Run Result | Fixed an issue where the (empty object) error is displayed even when entities are successfully created. |
| Run Result | Failed assertions with Continue assertions on failure ticked now do not block the test execution and continue to run the following assertion. |
| Run Result | The assertion results are now consistent with the assertions and are functioning properly. |
| Run Result | The value displayed under Duration in the Run Result page now displays the same value under Duration in the Details tab. |
| Run Result | The Filter Criteria in the Results module is now working properly. |
| Run Result | The values in the assertion module and Validation popup window now displays the same assertion URLs. |
| Run Result | Execution is now working properly when the value is updated in assertion during dataset level and when project variable is selected as an input. |
| Run Result | Fixed an issure where a success message is displayed when certain steps were not execute and assertion status is now working porperly. |
| Run Result | Fixed an issue where multiple executions in parallel remained in Queued runs. |
| Run Result | SFTP upload is now working properly even when the overwriteFileIfExisting node is false. |
Setting | The Settings page is now displayed properly. |
| Step | The Templates tab in the New Step popup window is now working properly after uploading or downloading files. |
| Step | The Templates tab is now enabled for the Upload and Download steps even after making changes. |
| Step | UI logs are now displaying properly. |
| Step | The Update button is now enabled and working properly when renaming the step File Upload and File Download step names. |
| Step | Fixed an issue where a validation disappears when saving a step. |
| Step | The Update button is now disabled when entering a new command and not selecting from the dropdown. |
| Step | The Save button is now disbaled after an invalid file upload. |
| Step | Appropriate error messages are now displayed after running a query in unit testing when an incorrect value is entered. |
| Step | The verifyElementPresent and verifyElementNotPresent commands are now displayed and working properly. |
| Test Flow | Fixed an issue where newly-created test flows cannot be saved. |
| Test Flow | Fixed an issue where query assertion nods were not displayed in the Assertion Inputs popup window. |
| Test Flow | Fixed an issue where the Sync button is still displayed even after turning off the TestRail integration. |
| Test Flow | Fixed an issue where a new tab in the browser is opened after clicking the Run button in the Run Setup Form. |
| Test Flow | Test flow with multiple scenarios can now be synced with TestRail. |
| Test Flow | A warning message is now displayed when updating steps associated with a scenario. |
| Test Flow | Cloning is now required when updating steps associated with a scenario. |
| Test Flow | Fixed an issue where a duplicate test flow can be created. |
| Test Flow | Entering a name in the Create / Select Step dropdown now only suggests existing steps instead of the Rename to [Name] button. |
| Test Flow | The assertion and scenario filters in the Flow module are now working properly. |
Test Automation 3.3.0
Release Date: 11 June 2025
New Features
This section provides the list of new features and enhancements that have been added in this release.
| Affected module | Description | Flow | An option to sync a test run to the TestRail automatically is now available in the Run Setup Form. |
|---|---|
| Project | Projects from a TestRail can now be used in Test Automation. Additionally, the test cases within a project can now be synced. |
| Project | A Test Case Management section allowing you to select the application and TestRail project for integration is now available in the Integrations tab. |
| Report | Minio properties are now in a yaml file. |
| Report | The report now displays only the commands with screenshots. |
| Report | Command descriptions are now displayed instead of the xpaths. | Report | When generating a report, the Report Name field is automatically filled with a value that can be edited. | Report | Sections to be included in the report can now be specified. | Report | Separate files for each dataset used in the test execution can now be generated. | Report | A frontend-generated summary report can now be downloaded by clicking the Download Run Summary button. | Report | The live feed of test results now automatically retries when requests fail or time out. | Results | The TestRail run status can now be viewed in the Run Results screen only if the Sync Run feature is enabled. |
| Settings | A new Integrations page has been added to the Settings module. This page allows users to enable or disable the integration of applications with Test Automation. Additionally, it provides an overview of the integration status for each application. |
| Step | A search option has been added to the catalog popup for selecting services. |
| Step | The process dates for newly created batch step templates are now shown as one day before the business date. |
| Step | The String source type can now handle empty string and date format default settings during template creation. |
| Step Test Flow |
The behavior of the Apply to Step and Update buttons has been improved. |
| Step Test Flow |
The rename to step feature has been removed and the behavior is now automatically applied when clicking the Update or Save button. |
| Step Test Flow |
Creating a template is now simplified. |
Fixed Issues
This section provides the list of issues that have been fixed in this release.
| Affected module | Description |
|---|---|
| Assertion | The Rest Catalogue is now available and displays the correct items. |
| Dataset | Fixed an issue when uploading a bulk dataset. |
| Dataset | Fixed the indicated supported file format from .side to .xlsx when uploading a bulk dataset. |
| Dataset | Fixed an issue where the contents of the dataset are not updating without refreshing. |
| Dataset | Fixed an issue where the user input variable name is set as the Source Value if the template containing that variable is selected in the dataset. |
| Flow | Fixed an issue where a test flow with steps from 2 different versions cannot be executed. |
| Flow | The step linking is now working for two different scenarios with the same steps. |
| Flow | Fixed an issue where deleting a flow in a version also deletes the same flow in other versions where it is configured. |
| Flow | The node name is now displayed correctly for API steps. |
| Login | Password can now be reset. |
| Project | All images and icons are now properly displayed in TA. |
| Project | Fixed an issue where the click area of the next and previous page icons overlap. |
| Report | The sequence of the UI steps in the report is now fixed. |
| Results | Fixed an issue where the uploaded and downloaded files were not visible after SFTP execution. |
| Results | Fixed an issue where the variable values are not visible in the UI logs. |
| Results | Fixed an issue where some UI logs are displayed as assertions. |
| Results | Fixed an issue where the step level value was being used when executing an API step with query parameters. |
| Results | Fixed an issue where execution remained in the queue even if it was already in progress or completed. |
| Results | Descriptions are now displayed in the UI logs. |
| Results | Fixed an issue where active run results are not being fetched. |
| Results | Fixed an issue where an error message is displayed when using an OCULAR authentication type is used during execution. |
| Results | Filters for Test Flow, Dataset, Environment, and Status are now available in the Run List and Run Graph. |
| Results | The SFTP file upload reports can now be downloaded. |
| Results | The Store Attribute command is now working properly. |
| Results | Fixed an issue where an empty Response Body is returned for Batch and API steps. |
| Results | The Verify Text command is now working properly. |
| Results | Fixed an issue where executing a batch with API or Query assertions is failing. |
| Results | The assertion headers are now displayed properly. | Step | Fixed an issue where a command can be entered even if it is not in the dropdown list. |
| Step | The Templates tab is now enabled for the Upload and Download steps even after making changes. |
| Step | Fixed an issue where the Save button is still enabled even after an invalid file was uploaded. |
| Step | Fixed several issues where tabs and buttons are enabled even if some of the required fields are not supplied yet. |
| Step | The beautify functionality is now working for the Query step. |
| Step | Fixed an issue where the template is not visible after navigating to the Templates tab during step creation. |
| Step | A notification now appears for unsaved change when navigating to a different page. |
| Step | Fixed an issue where a validation disappears when saving a step. |
Test Automation 3.2.0
Release Date: 05 May 2025
New Features
This section provides the list of new features and enhancements that have been added in this release.
| Affected module | Description |
|---|---|
| Assertion Dataset Flow Project Step |
Modules displayed in the left menu are now limited by the configured authorization. |
| Dataset | Default dataset template is now required to be provided when creating or updating a dataset. |
| Dataset | New random data is now automatically generated for every execution without changing the request field manually every time. |
| Dataset |
File details that are displayed in the Step module are now displayed in the Dataset module as well. |
| Dataset | The CONTAIN operator can now be used in configuring assertions. |
| Dataset Flow |
Database can now be specified for each scenario. |
| Flow | A new File Download or File Upload step node can now be added in a flow. |
| Flow | The _ and - characters can now be added to a Scenario description. |
| Flow Results |
Test flow executions are now faster. |
| Project | A default database can now be configured for a project. | Results | The database name is now displayed in the Overall Scenario Summary section of the Results page when a scenario has a Query step. |
| Results | A successful file upload or download is now displaying as Step Completed in the Results page. The uploaded or downloaded file is still present. |
| Results | The value for the Storage Type field is now displayed in the Results page. |
| Results | The Step Failed details are now displayed in the Results page. |
| Results | File Download and File Upload steps are now displayed in the Results tab. The downloaded or uploaded files can be viewed in the Details and Attachments tabs. |
| Step | The UI/X of the SFTP step type configuration page is now updated. |
| Step | A File Download and File Upload steps types are now available. |
| Step | A step dataset template is now generated after creating a File Download or a File Upload step. |
| Step | If no application URL is configured, the specified URL in the SIDE file will be captured. |
| Step | Variables are now accepted as input values in commands. |
| Step | Execution of UI step types is not working properly. |
| Step | SFTP upload files can now be overwritten. It also triggers an automatic update to the dataset template. |
| Step | A new ORDS step type is now available. |
Fixed Issues
This section provides the list of issues that have been fixed in this release.
| Affected module | Description |
|---|---|
| Assertion | Fixed an issue where the success message popup appeared multiple times after updating an assertion. |
| Assertion | A Query type assertion can now be created. |
| Assertion | API assertions with path parameters can now be created. |
| Dataset | Assertions in dataset can now be updated and reused in test executions. |
| Dataset | The Test Flow Variable is now available in the Node Type dropdown list. |
| Dataset | Fixed an issue where a duplication error message appears when creating a new dataset. |
| Dataset Flow |
Sequence of entities in test flow and in excel template are now matching. |
| Flow | Fixed an issue where steps linked to a specific version in a default environment were unavailable when creating a new test flow with either no configured environment or a different one. |
| Flow | Fixed an issue where API steps with path parameters cannot be linked. |
| Flow | Fixed an issue where a new tab is being opened when clicking the Run button. |
| Flow |
Fixed an issue where IWS were not being imported through the REST catalog. |
| Flow | Fixed an issue where the input and output values were not being loading when creating a query assertion in the Flow module. |
| Flow | Dataset sidebar in the Flow module is now displaying the expected data. |
| Flow | Fixed an issue where a clone error message appeared when updating a step description that is not used in any scenario or flow. |
| Flow | Path parameters of assertions are now displayed when creating a test flow. |
| Flow | Fixed an issue where a newly-created assertion is linked to a different project that is opened in another tab. |
| Flow | Fixed the notification message when adding a new scenario to a test flow. |
| Flow | Fixed an issue where existing steps were not imported to the test flow. |
| Project Results |
Secret values are now hidden in Step request and response payloads. |
| Project Step |
The default template name is now updated when switching from one verstion to another. |
| Project Step |
Fixed an issue where a newly created step was linked to a different project. |
| Results | Fixed an issue where an API step with assertions and multiple datasets executed only one dataset. |
| Results | Test executions now display the correct status. |
| Results | Configured assertions in the Flow module are now displayed in the Results module. |
| Results | Fixed an issue where UI logs were duplicated after executing a UI test flow. |
| Results | Actual values for Verify value command are now displayed in the Results page. |
| Results | Fixed an issue where newly created test flow results were not displayed in the Results module. |
| Results | Fixed an issue where assertion details were not displayed for scenarios with multiple steps, each or at least one step having an assertion. |
| Results | Fixed an issue where test execution details could not be accessed in the Results module until the execution was finished. |
| Results | Fixed an issue where test flows were in Queued runs when the test only have a UI step, and logs were not appearing in the Results module for tests that contain other step types. |
| Results | UI steps with configured assertions are now running properly. |
| Results | API steps with configured assertions are now running properly. |
| Results | The Started at label is now replaced with Ended at. |
| Results | Secret values are now hidden in the UI logs. |
| Results Step |
Same versions can now be created in different projects. |
| Results Step |
The live execution run results are now displayed properly. |
| Results | Fixed an issue where a UI step failed during flow execution but passed in the step module run. |
| Results | Assertion payloads are now displayed correctly, even if at least one assertion has failed. |
| Results | Fixed an issue where the latest results are not fetched unless the refresh button is clicked. |
| Results | Fixed an issue where failing tests were marked as Passed. |
| Results | Warnings for verify commands are now added to the test execution logs. |
| Results | Warnings for verify commands are now added to the test execution logs. |
| Results | Fixed an issue where details get mixed up when two different project names with identical project codes were executed in separate environments. |
| Results | The number of passing and failing dataset executions are now displayed correctly in the Results page. |
| Results | The Run By field is now displaying the correct value. |
| Results | Fixed issues found during batch executions in multiple tenants. |
| Step | Fixed an issue where the screenshot for the last command was not being displayed. |
| Step | A template is now automatically removed from the list when deleted. |
| Step | The verifyText command is now working as expected. |
| Step | Fixed an isse where commented commands were still executed. |
| Step | Fixed an issue where the Update button remained enabled even if an error was found in the Response Body. |
| Step | The dataset used to excecute the query is now saved to the default template of that query. |
| Step | Batch parameters are now placed properly in the batch template. |
| Step | Fixed an issue where the template cannot be saved details were populated before the template name. |
| Step | Fixed the search functionality for SFTP where it is not returning a file matching the search criteria. |