Release Notes - Assure v25.1.1
Avo teams brings the release of the new version v25.1.1. With this new version, user can improve the user experience by using latest features.
Important: As a part of this release, downloading the latest version of the Avo Assure Client is mandatory to ensure full compatibility and optimal performance. Please refer steps to Download Avo Assure Client
Key Enhancement
Feature
Description
Data Table Access Control
Data Tables in Avo Assure were editable by all users, resulting in test data conflicts.
With the new enhancement, the user who creates a data table can assign a specific user with editing access. No other users, apart from the assigned one, will be able to make changes. Only one person can be assigned to a data table at a time.
Manual Element Creation feature is available for Desktop
This enhancement allows users to manually create elements for desktop. Earlier, this feature was available only for the web.
Excel Action - Retrieve Data from Row
Get Param – Supports Additional Parameter (ADV)
Test data in Excel was difficult to read since all data had to be entered in a single row. To address this, the new enhancement requires the user to provide an additional parameter (ADV) after the input syntax. This improves readability.
Better provision to understand Excel Sheet
Due to multiple test cases in Excel, it is difficult to understand which test step group belongs to which test case.
With the enhancement in the Get Param action, this issue has been resolved.
Better maintenance of test data and sheets in excel
Maintaining test data was challenging as each scenario had to be recorded in a separate sheet, leading to multiple spreadsheets that were difficult to manage.
With the enhancement in the Get Param action, this issue has been resolved.
Added two default custom property rows in Element Identifier
Multiple environment execution on QA, Dev and UAT
With this enhancement, users can execute the same script in multiple environments by providing the Excel sheet path in the input value field within the execution tab, instead of changing it manually in Test Steps each time.
Date Picker Functionality
The date picker functionality is a low-code custom action. Users write low code inside the Code Editor within the "Create Custom Action" popup to automate the calendar and fetch data such as the date, day, or year.
"Error Details" column added for failed Test Step
In the reports, there was no detailed description of failed Test Step to understand the reasons for failure.
Dynamic PDF reading is supported.
Two default custom property rows added in Element Identifier window
With this new enhancement user will get two rows as custom properties in Element Identifier window, where user can add any html properties as per their requirement.
If/Else supports string operators like contains, length, replace, and find
With this new enhancement, If/Else will support string operators like contains, not contains, length, replace, find etc. This will make extracting and filtering data from tables easier.
Nested loops are supported in the "For" condition
Provision to write in data tables
There was no option to write in data tables.
With this new enhancement, users can write back to a data table by providing syntax in the input field available in a Test Step under the Test Step Group
PDF format reports are supported in emails
Users were unable to access the link in email reports. With this new enhancement, reports will now be sent via email in PDF format, containing execution details.
Bug Fixes and Improvements:
Refer to the table below to learn more about the bugs addressed along with the respective benefits.
Recorded scenario is failing
The recorded scenario was failing because the user was unable to click on links and select default values from the dropdown menu. This issue is now resolved.
Screenshots are not getting captured properly
Elements in screenshots were not captured properly. With new enhancement, the captured item will be highlighted in the screenshot, making it easier for users to identify each element on the screen.
SetTextBox values were not entered properly during debugging
While capturing elements, User is unable to enter the value in the Text Box. This issue is resolved
Element not clickable after recording Though it's visible on the page
After recording a scenario using Avo Genius, the user was unable to click on the recorded elements, though it's visible on the page. This issue is now resolved.
Elements are not traced with default values while recording the test case but getting passed in client console during debugging.
Elements were not getting captured on the client console at time of recording, but they were executed while debugging. This issue is resolved
Elements are not traced with default values while recording the test case
Elements were not traced with default values during recording but passed in the client console during debugging. This issue is resolved. Now elements are being traced properly and executing as expected.
Avo Assure does not support the validation of a pdf which opens in a new browser instance
Avo Assure now supports validating PDFs that open in a new browser instance. This is possible with the Read PDF Action, which allows extraction and validation of pdf
Widget elements are not getting verified
Elements were captured as tables, however, upon inspection, they appeared in a different format, preventing element verification. To resolve this, Avo Assure provides the following low-code actions:
Compare_Json_Input
Compare Json and UI
Compare Widget with Json
Multi-Environment execution of an application in different instances with the same script is not possible in Avo
With the new release, this issue is resolved, and users can execute the same script in multiple environments by providing the Excel sheet path in the input value field within the execution tab, instead of changing it manually in Test Steps each time.
HTML/PDF/JSON/PDF with Screenshot Report - There is no details provided for failed test step
In report, details were not provided for failed test steps.
This issue has been resolved with the addition of a new column called "Error Details," which provides a concise description of each failed test step.
Note: Some tickets were resolved in the last release. Please refer to the Release Notes - Assure v25.1.0 for details on the following tickets: CQX-202, CQX-204, CQX-205, CQX-206, and CQX-209.
Explained fixes are intended to improve the overall performance and usability of the platform, addressing key issues reported by users.
We hope these changes in Avo Assure version 25.1.1 enhance your experience with the platform
Last updated
Was this helpful?