Release Notes - Assure v25.5.5
Avo is excited to announce the release of new version 25.5.5. Here are the enhancements:
Bug Fixes and Improvements
See the following table for the bugs resolved and the key benefits.
Fixed Issue with User Management in Vertical Admin Section
User Management module under Vertical Admin was also displaying users which belongs to other verticals. This issue is resolved, and User Management module only displays the user who belongs to the same vertical.
Fixed Click on Table Cell Action Issue for Hidden Rows
Click on Table Cell action was not selecting hidden rows correctly for some table rows. This issue is resolved, and the action now clicks on the specified cell correctly, when hidden rows are present.
Fixed Missing Scenario Names in Selenium Reports
Selenium reports were showing only the first scenario name. The remaining scenarios showed “scenario is started” without their actual names, which made result analysis difficult. This issue is resolved, and the reports now display each scenario name.
Fixed Issue with Test Case Execution Time Between Client and Agent
The agent was taking more time to run Test cases compared to the client and took longer wait time when something failed. This issue is resolved, and the agent now runs Test cases faster and closer to the client’s execution time.
Fixed Issue with Execution Pipelines
When you triggered the execution of many Test cases, a few Test cases got stuck in the In Progress state permanently. No reports were generated for those Test cases. This issue is resolved, and executions run smoothly and reports are generated.
The weekly execution on Virtual Machine via agent was showing a status of In Progress, while the agent indicated completion. Additionally, no email reports were received. This issue is resolved, and execution status shows as expected and email reports are generated.
Fixed Issue with Add Client Certificate Action
When Add client certificate action is used, Avo Assure client was throwing error invalid number of inputs provided. This issue is resolved, and Add client certificate action works as expected which allows users to pass the client certificate at the Test case level for API authentication.
Last updated
Was this helpful?