Release Notes - Assure v26.5.1
Avo is excited to announce the release of new version 26.5.1. Here are the enhancements and bug fixes:
Key Enhancements
Versioning Support for Azure DevOps
You can now configure Azure DevOps in the Versioning page and manage test artifacts directly from Design Studio. This integration supports push, pull, and compare operations for Element Repository, Test Data Management, Test Case, Reusable Library, E2E Flow, and Execution. Azure DevOps icons and status indicators are also displayed to help track artifact versioning. Learn more
Enhanced Get Key Value and Get Tag Value Action Syntax
The Get Key Value and Get Tag Value actions now use an input format that accepts only two parameters, the JSON or XML input, and the corresponding key or tag path. You can now automatically generate the required path using the Data Path Builder, making script creation easier and faster. Existing scripts using the old syntax continue to work for backward compatibility. The new syntax is recommended for all new scripts. Learn more
Bug Fixes and Improvements
See the following table for the bugs resolved and the key benefits.
Fixed Issue with Select Menu Action Status in Desktop Applications
The Select Menu action performed successfully, but the execution report incorrectly marked the step as failed. This issue is resolved, and the report now displays the correct execution status.
Fixed Issue with Add Element in Webservices
When using the Add Element feature in Webservices, re-adding a deleted element incorrectly replaced the name of another existing element. This issue is resolved, and re-adding an element now preserves the names of all existing elements.
Fixed Issue with Agent and Grid Selection Display in Execution Configuration
Selected Agents and Grids were not displayed in the Execution Configuration window after saving or refreshing the page. This issue is resolved, and the selected agents and grids now display correctly after saving and page refresh.
Fixed Issue with Custom Action Created from Reusable Test Step Group
The newly created Custom Action from a Reusable Test Step Group showed an Invalid Keyword error during execution. This issue is resolved, and newly created Custom Action now executes successfully.
Last updated