Release Notes - Assure v26.5.4
Avo is excited to announce the release of version 26.5.4. This release notes provide an overview of the updates included in this version, helping you stay informed about the latest changes in Avo Assure.
Key Enhancements
Support Opening Avo Assure in Multiple Browser Tabs
You can now open and use Avo Assure in multiple browser tabs or windows at the same time. You will no longer see the Only one session allowed message, and your session remains active across all open tabs. This allows you to switch between different modules or tasks more efficiently without signing in again or interrupting your work. Learn more
Supports Deep Links for Test Cases, Reusable Library, and End-to-End (E2E) Flows
You can now use the Copy Link option to generate a direct link for Test Cases, Reusable Library items, and End-to-End (E2E) flows. Open the link to access the specific artifact directly without navigating through the project structure. You can also share the link with team members or bookmark it for quick access, making navigation more efficient. Learn more
Enhanced Change Password Process
You can now change your password from the Profile menu by first verifying your current password before entering a new one. The updated process provides clear validation and step-by-step guidance, helping you update your password securely, reduce errors, and complete the password change process with confidence. Learn more
Improve Test Artifact Context Menu for Versioning Actions
The context menu displayed when you select the Ellipsis icon(...) for artifacts such as Element Repository, Test Cases, Reusable Library, End-to-End (E2E) flows, Execution, and Test Data Management now uses consistent and meaningful option names. Version control actions are displayed with the configured integration name, such as Bitbucket actions or Azure DevOps actions, and are hidden when versioning is not configured. This makes it easier to identify available actions, reduces confusion, and provides a more consistent experience across Avo Assure. Learn more
Avo Assure Supports Automatic Updates for Avo Client and Avo Agent
The Avo Client and Avo Agent now automatically updates with the latest improvements, ensuring a smoother transition and a consistent agent experience without requiring manual intervention. Learn more
Bug Fixes and Improvements
See the following table for the bugs resolved and the key benefits.
Fixed Issue with Error Message Displayed When Pulling Test Cases from Bitbucket
An error message was displayed while pulling a test case from Bitbucket in the Test Case page, while the pull operation was completed successfully in the background. This issue is resolved, and test cases now pull successfully without displaying an error message.
Fixed Issue with Automatic Removal of Test Cases from Execution Lists
Test Cases were removed automatically from an Execution List. This issue is resolved, and Test Cases are no longer removed automatically. When you remove a Test Case, the change is correctly recorded in the Audit Log.
Fixed Issue with Performing Actions on Elements
When you performed actions on elements, some elements were not identified correctly, causing actions such as Click Element, Set Text, Send Keystroke Value, and Verify Exists to fail. This issue is resolved, and these actions now work as expected.
Fixed Issue with Incorrect Server URL in the Downloaded Agent
When you downloaded an Avo Agent, the ai_server URL in the agent configuration did not match the associated Avo Assure instance, causing IRIS actions to fail during execution. This issue is resolved, and the downloaded agent now uses the correct URL for the corresponding Avo Assure instance.
Fixed Issue with IRIS Actions Execution
The Click IRIS action did not work consistently during Agent and Client executions. These actions reported a successful execution without performing the action. This issue is resolved, and the Click IRIS action now work as expected.
Fixed Issue with Self-Healing Element Identification
Self-Healing did not identify the correct elements in some scenarios, such as after element attributes changed, when executing steps after a healed element, or when multiple elements on the same page shared the same Data Element ID.
This caused Self-Healing to retrieve incorrect values or interact with the wrong element. This issue is resolved. Self-Healing now identifies the correct elements and performs actions more reliably.
Fixed Issue with Bitbucket Integration Configuration
Configuring Bitbucket integration for new projects did not work as expected. This issue is resolved, and the integration can now be configured successfully.
Last updated