Release Notes - Assure v25.2.0
Avo teams brings the release of the new version v25.2.0. With this new version, user can improve the user experience by using latest features.
Please note that individual page link for some enhancements is still in progress. Once completed, we will notify you. Thank you for your patience.
Key Enhancement
Object verification is not supported
User should be able to validate whether fetched data belongs to specified column based on the provided input and also verify the data against the expected value.
Bitbucket Enhancement-
There is no back up if test data/excel gets deleted in case
This ticket includes the below Bitbucket Enhancement: •Ability for users to connect Bitbucket using user id and PAT to the corresponding Repository
•Ability for the users to select Element Repository /Test Case/test data and commit / override to Bitbucket in Main / their specific repositories
•Ability for users to view all the versions of a Repository. User will be able to pull from any version in Avo Assure.
•Project Manager will be able to connect to Master repository to view all versions and pull any specific version, if required and commit
•Verify CT execution trigger gets Avo Assure Test Cases from Bitbucket
•A mechanism for uploading supporting documents, like test data, must be provided once Test Cases are committed to Bitbucket.
•A mechanism for test engineers or leads to commit their changes to their local branches in Bitbucket must be provided. Additionally, after the Test Case is finished, they can raise a review request or notification mechanism to the project manager.
•Avo Assure will have a version comparison method so that project managers can examine the version before committing to the master branch.
Zephyr Scale Enhancement
This ticket includes the below Zephyr Scale Enhancement: •Ability for users to login to Zephyr Scale using Jira PAT. In Avo Assure, users will be able to view all Jira projects
•Verify proper mapping of Test Cases. In Avo Assure, users will be able to view all the Test Cases that are created in Zephyr Scale
•Verify Test Cases are added to execution profile and able to select Zephyr Scale as an integration option
•Verify users can select the Test Plan and Test Cycle in Execution profile, that are created in Zephyr Scale
•Verify users can create new Test Cycle in Execution Profile under a Test Plan. User will be able to view the newly created Test Cycle in Zephyr Scale
•Verify status is updated to Zephyr Scale
•Create a separate record in Zephyr Scale for status updates, if the user does the test cycle using the same one.
•Verify defect is logged in Jira and linked to corresponding Zephyr Scale Test Case
•If user re-run the execution with the existing Test Plan and Test Cycle configuration, Avo Assure will update the previous run data
•Logged Defect is visible in Jira
Update the Type field to automated in Zephyr Scale Test Case as soon as it is mapped in Avo Assure
Self-Healing is now working for custom attributes
During execution any changes in attribute found, it will automatically update in the element repository after the execution
Re-run enabled for failed Test Cases
Below are the enhancements covered in this ticket: •If user want to rerun the failed testcases (After complete run), they should enabled Re-Run failed Test Case toggle button from the Execution profile
• If Re-Run failed testcase toggle button is enabled, user can select the number of times, it needs to rerun failed testcases (Options will 1 to 5). Each re-run will consider only the failed Test Cases of previous run
•When a Test Case is re-run, it will override the current Test Case level report
Note: This option will run all the Test Cases in the profile and then collect all failed testcases to re-run
Switching tabs and editing values while debugging is possible
Previously, while debugging Test Steps in Avo Assure, users were unable to edit any Test Case value or unable to navigate different tabs. With this enhancement, users can now navigate to other tabs and make also changes in the Test Case—but these changes or modifications will be applied in the next debug.
Additionally, with this enhancement, the Stepwise Debug and Run from Step features now work at the Test Case level. Previously, these methods only applied to Test Step Groups, but they are now available for entire Test Cases as well.
Bitbucket Enhancement-
No Code Repository
Below are the enhancements covered in this ticket: •Ability for users to connect Bitbucket using user id and PAT to the corresponding Repository
•Ability for the users select Element Repository /Test Case/test data and commit / override to Bitbucket in Main / their specific repositories
•Ability for users to view all the versions of a Repository. User should be able to pull from any version in Avo Assure.
•Project Manager should be able to connect to Master repository to view all versions and pull any specific version, if required and commit
•Verify CT execution trigger gets Avo Assure Test Cases from Bitbucket
•A mechanism for uploading supporting documents, like test data, must be provided once Test Cases are committed to Bitbucket.
•A mechanism for test engineers or leads to commit their changes to their local branches in Bitbucket must be provided. Additionally, after the Test Case is finished, they can raise a PR or notification mechanism to the PM.
•Avo Assure must have a version comparison method so that PMs can examine the version before committing to the master branch.
Provide custom attribute name in client setting
In this enhancement user can provided the element attribute name in the setting section of Avo client based on the user input the element attribute value will be identified and prioritize while capturing the elements.
Detailed description of failed test cases in reports
For all the verify keywords, users can view detailed error information for failed test cases. The error details are displayed in the "Error Details" column of the view report. This feature is applicable only to failed test cases; no information is shown for passed cases.
Grid action - Sort Table
Bitbucket Enhancement-
No version control tool to manage checkins checkouts from each resources
Below are the enhancements covered in this ticket:
•Ability for the users select Element Repository or Test case and commit / override to Bitbucket in Main / their specific repositories
•Ability for users to view all the versions of a Repository. User should be able to pull from any version in Avo Assure.
•Project Manager should be able to connect to Master repository to view all versions and pull any specific version, if required and commit
•A mechanism for uploading supporting documents, like test data, must be provided once test cases are committed to Bitbucket.
•A mechanism for test engineers or leads to commit their changes to their local branches in Bitbucket must be provided. Additionally, after the test case is finished, they can raise a PR or notification mechanism to the PM.
•Avo Assure must have a version comparison method so that PMs can examine the version before committing to the master branch.
GRID Action - Verify Column Value
Grid Action - Verify Table Sort
PDF Support - Saving downloaded pdf with blob URL in your system is not working
With this enhancement, the user can open the URL in a new tab, where the PDF will be automatically downloaded to the local system.
Enhancement in custom attributes
Case Sensitivity is removed for Folder Search/ data table search
With this new enhancement, User can search with a particular text, and all the items that contain that text will appear. Items searched are not case sensitive
Get Total Column Count
Suppose in a grid, 6 columns are visible in UI, but the entire grid contains 14 columns in the UI. In such cases, pass the visible command in the Total Column Count action. When you debug it, all 6 columns will be visible as per the UI.
Bug Fixes and Improvements:
Recorded scenario is failing
Users can now easily click on the website link to navigate to the appropriate application and also, select the required value from the dropdown menu
SetTextBox values were not entered properly during debugging
Users were unable to enter text in certain textboxes when recorded using Genius. This issue has now been resolved, now users can successfully enter text in the textbox, and the logs in the client console will correctly display the action as run successfully
Elements are not traced with default values while recording the Test Case
The dropdown name is not displaying as per its label. If users want to give the appropriate name to the captured element, they can do so in the Element Repository's instead of list items.
Avo does not support the validation of a pdf which opens in a new browser instance
The user was unable to read content from a PDF opened in a new tab. This issue has now been resolved, as the user can use the Read PDF actions to read and and validate the pdf which opens in a new tab
The element repository intermittently takes a long time to load
While switching the tabs the pages are taking time to load so this issue is resolved
Duplicate elements in element repository after importing the Test Cases
When Test Case is imported Element Repository associated with Test Case is also being imported this is causing duplication of elements now this issue is resolved, and user will get checkbox to select whether element repository should be imported or not while importing any Test Case
HTML/PDF/JSON/PDF with Screenshot Report were not available for a failed step with description
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. These reports can be downloaded in HTML/PDF/JSON/PDF with Screenshot and email notification report as well.
It was not possible to verify the table content on the desktop applications
With new enhancement, It is possible to verify the table content on the desktop applications. Users can validate if particular text is visible in the table along with the column header. All table-related functions such as GET Row Count, GET Column Count, GET Cell Value, GET Row Data, verify column value etc. are now supported on desktop applications.
Select Menu is not working for multi-level menu selection.
This issue has been resolved:
User will be able to select a multi-level menu.
The Select Menu will work for two, three, four level menu depending on the tree structure that is available in the application
Multi select can be done using sendfunctionkeys
When we add reusable module, edit some input value and change the sequence of step in the reusable library, it is not getting reflected in Test cases
This issue has been resolved:
If we change the sequence of step - it will be reflected on test cases where this is used.
If we change the input value - it will be reflected on test cases where we have not edited its input, and it will not change the input for the testcases where we have changed the input of the step.
If we skipped the step in reusable module, it will be reflected on every usage of it in test cases.
If we delete a step from reusable module, it will get deleted from everywhere from test cases where we have used it.
Refer to the table below to learn more about the bugs addressed along with the respective benefits.
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 v25.2.0 enhance your experience with the platform
Last updated
Was this helpful?