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.
Note:
Please download the Avo Integrator extension using the Chrome web browser to work with Zephyr Scale and JIRA integration. Currently, this extension is only available for Chrome. Learn more
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 Test Cases (After complete run), they should enabled Re-Run failed Test Case toggle button from the Execution profile
If Re-Run failed Test Case toggle button is enabled, user can select the number of times, it needs to rerun failed Test Cases (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 Test Cases to re-run Learn more
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. Learn more
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 Assure client based on the user input the element attribute value will be identified and prioritize while capturing the elements. Learn more
Detailed description of failed Test Cases in reports
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
This action sorts the grid columns values in the order provided in input syntax, user can arrange the columns in ascending/ descending order for different values like dates, numbers, alphanumeric, alphabets etc. Learn more
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
This action validates whether a value exists in all rows of the selected column in the grid. If 'All Row' is not specified in the input syntax, the action defaults to searching for the specified value in any row of the grid. Learn more
Grid Action - Verify Table Sort
This action verifies the sort applied on a column in the specified order provided in the input for numeric, alphanumeric, alphabetical and date types of columns. Learn more
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
With this new enhancement, users can edit the name and value of a custom attribute and identify elements using the element locator in custom attribute. The attribute name will also appear in the console and reports for user reference after debug and execution. Self-heal will also be applied to custom attributes Learn more
Case Sensitivity is removed for Folder Search/ data table search
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.
CT Enhancement
Zephyr scale
Integration and login with the Data Center version are also supported.
In the Data Center version, when Avo Assure Test Case is mapped to a Zephyr Scale Test Case, it can also be linked to a Jira user story, with the story details stored for future defect logging.
A test cycle can be pulled from Zephyr Scale and selected for mapping.
A Test Case can be created in Zephyr Scale directly from Avo Assure, and the created test case will have the same name as the one in Avo Assure.
A toggle button is available to automatically create a defect when a Test Step fails; alternatively, defects can also be created manually.
The auto defect configuration toggle button can be enabled while creating the execution list to automatically log a bug for any failed Test Step.
Mapped Test Cases can be searched by Test Case ID or Test Case name in the View Mapping tab.
During mapping, the Zephyr Scale Test Case ID will be displayed alongside the Test Case name.
Limitations will be set, then lazy loading will be going to reduce
User can now be able to search Folder names for Avo Assure and Zephyr Scale folder names. Once searched folder, then only that folder will be highlighted
After execution, the updated status and the time taken for the execution can be viewed in Zephyr Scale. If any Test Step fails, the linked defect associated with the failure will also be displayed.
Once the execution is complete and a bug is created automatically, the linked User Story details can be viewed in the created bug in Jira
Test cases can be differentiated by their unique IDs, even if the Test Case names are similar.
User will get the status of re-run result and previous data won't be over written. new records will be generated for every execution
Mapped Test Cases can now be exported and imported in CSV file format.
In the Data Center version, screenshots will be attached to Zephyr Scale execution reports for the first failed Test Step.
While mapping, a Zephyr Scale Test Case can be created from Assure, and it will also be reflected in Zephyr Scale.
Bitbucket
With this enhancement, Execution tab and data Table can be integrated along with Element Repository and Test Case
User will get the option to globally push and pull Test Case, Element Repository, Execution Profile and Data Table by clicking bitbucket icon
Multiple users can integrate Bitbucket with their own credentials for the same project.
While selecting branches, a list of branches associated with Bitbucket will be displayed, and branches can also be searched from the list.
A commit message can be provided while committing any changes.
Files, including Excel sheets associated with the Test Case, can now be uploaded.
Users will be able to select items such as the Element Repository, Test Case, execution profile, or data table of their choice for pushing.
The Element Repository and Data Table associated with the Test Case can also be pushed by selecting the checkbox.
User will be able to view changes that are made while pushing
User will be able to provide message while pushing any items like Element Repository, Test Case, Execution Profile or Data Table
User will be able to push associated Test data and Element Repository with Test Case
While pushing any changes, user can send it for review to Quality Manager or Quality Lead who is also part of that project
Multiple users can integrate the bitbucket with their credentials for same project
While selecting branches, user will get the list of branches which are associated with Bitbucket and user can also search the branch from the list
While selecting branches, user will get the list of branches which are associated with Bitbucket and user can also search the branch from the list
User will be able to select a version to pull and will be asked to select the option to Override or to create new folder to restore. Restore will override the existing data.
When pulling items from Bitbucket, user will be able to override the existing Element Repository, Test Case, Execution Profile or Data Table
When pulling items from Bitbucket, user can create a same copy in the same folder
User will be able to create and pull folder and if Test Case from that folder includes any excel sheet, then that excel sheet will be downloaded to the mentioned path in get param action of the Test Step
User will be able to commit the changes to their local branch
User can send the version to Quality Manger or Quality Lead to review and commit it to Bitbucket
Reviewer can approve the review request and commit it to Bitbucket
After receiving a review request, the manager can reject the item from being committed and add a comment explaining the reason for the rejection.
Users can select a branch and version to compare Avo Test Cases, Element Repository, and Execution Profile against specific branches and versions in Bitbucket.
User can also compare associated Element Repository while comparing any Test Case
User will get the separate menu item for compare and they can compare any time before pull or push
User will be able to view all the commit history of the items by selecting version history option from the context menu after clicking on ... icon from tabs
Multiple reviewers can be added for any push request
Gen rocket
With this enhancement, Avo Assure can be integrated with Gen rocket to generate synthetic data efficiently by creating Data Table and integrating it with Avo Assure, user can fetch and generate synthetic data for the execution
In the execution configuration, the "Refresh Test Data Generation" toggle button can be enabled to generate new data for each execution.
User can also set limitation to iterate the test data for specific number of times
Harness
Assure Test Cases can be executed through Harness pipelines for CI/CT. For this, the code snippet for the cloud environment is copied and pasted wherever the image is pulled or a pipeline is created. Learn more
Jira
Automatically logged defects will be displayed in Jira reports and in Avo Assure reports with the defect ID
With the new enhancement, defects can now be logged manually in the Data Center version as well.
Taking the mandatory fields required to create a bug and storing them in the database for use during automatic bug logging
Bug Fixes and Improvements:
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.
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 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, we have introduced new action Click cell with this 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?