Release Notes - Assure v25.2.1
Avo teams brings the release of the new version v25.2.1. 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
Run the existing selenium automation scripts using Avo Assure
This feature includes the below enhancements:
Ability for users to write Test Cases respectively in Avo Assure, which in turn invoke SAFAL / GATS / Selenium Testcases from Avo Assure.
Ability for users to create required Execution Profile in Avo Assure and will be able to invoke through Harness Pipeline
Avo Assure is able to read and import SAFAL/GATS / Selenium execution report into Avo Assure
Possible to verify that test execution results are fed back in the pipeline (harness)
Test Case execution result are seen in Zephyr Scale
For failed Test Case, appropriate defects are created in JIRA
In Self-Healing element will be identified irrespective of their priority
Currently if the unchanged attribute is at top priority, then only it is identifying and updating the other values.
With this enhancement, element will be identified irrespective of their priority and the changed attribute values will be updated during execution.
Generate report and run only failed scenarios
Currently halt option was not considered for rerun since it used to halt the complete execution. With this enhancement,
It has been enhanced and rerun of failed Test Cases is also possible for halt option.
Rerun option is provided in reports. Upon clicking user can rerun the failed Test Cases based on the inputs provided in execution profile for rerun of failed testcases.
Possible to find the references of elements from element repository in the project using Information button
This feature includes the below enhancements:
In element repository against each element information button will be displayed.
By clicking on info button, pop up will appear with list of Test Cases along with the folder path.
This pop up will also display the number of Test Cases where the element is being referred.
User will be able to navigate to Test Cases by clicking on the Test Case name.
Possible to find the references of reusable Test groups in the project using information button
This feature includes the below enhancements:
In the reusable library against each element information button will be displayed.
By clicking on info button, pop up will appear with list of Test Cases along with the folder path.
This pop up will also display the number of Test Cases where the reused Test Step group is being referred.
It will also display the number of times the reused Test Step group is referred in that Test Case along with whether the I/O value is modified or not.
User will be able to navigate to Test Cases by clicking on the Test Case name.
Failed Test Cases can be rerun by using rerun option
This feature includes the below enhancements:
User needs to create an execution with failed Test Cases (If there is no failed testcases, it should display a message)
User are allowed to change settings from a toggle button in Test Case execution configuration
Rerun option should be available for the execution, which are completed or terminated
Users are allowed to create executions with failed Test Cases from previous runs.
Pop-up will list all the failed Test Cases with auto selected and option for user to select the re-run count
User will be able to remove Test Cases for Re-run and select the re-run count.
Grid Action- Get Column Data
With this enhancement,
Get Column Data action is provided which will give total visible row count from the grid. In input user need to pass "visible" to get the exact row count as per the UI.
for eg: If the grid has 10 pages and its currently on the page number 1 and it has 20 rows then "get total visible row count" action will give count as 20
Grid Action- Sort Table
This feature includes the below enhancements:
Sort Table action will sort a grid column values with given order (ascending or descending)
It is applicable for all the different values- dates, numbers, alphanumeric, alphabets etc.
Detailed description of failed Test Cases in reports
This feature includes the below enhancements:
Reports will give detailed "error description" for the failed steps in all the report format like HTML, PDF, detailed PDF, and email notification report as well.
We are providing the error details for Grid, Excel, textbox operations, Dropdown and radio checkbox operations related keywords in this release
Bitbucket Enhancement
This Bitbucket feature includes the below enhancements:
Avo Assure has included a Test Case assignment functionality, where in Manager can assign Testcases to different team members (One test case per person). This functionality can be used to restrict Testcases getting overwritten by other users.
Each user (based on his login) can select the branch and version, and compare Avo Test Cases, Element repository, Execution profile against Specific branch and versions in Bitbucket. Also, while comparing Test Cases user can also compare and view associated Element repository.
Compare will be a separate menu item. User can compare anytime (Before Pull, Before Push) and can Pull the respective Test Cases. While pulling users should be able to:
1. Override existing Test Case/Element Repository/ Execution profile/Data table
2. Create a copy in the same folder (with date appended)
3. Create a folder and pull
Note: If Test Case has used Test Data excel sheet, this will be downloaded to the path mentioned in get param keyword of the Test Step. Each user (based on his login) can select the branch and version to Push. During the push user should be able to view changes made, provide push comments and optionally, for a Test Case push, select the associated items such as Test data and Element Repository. Also, Request for review and approval to the desired manager is also possible.
User will be able to get the branches while pushing the Test Cases.
CT Enhancement
Note:
These enhancements are applicable to Orchestration Items like Selenium, Safal, Cucumber, TestNG and Karate
Orchestration
invokePlatform is action which invokes or executes the scripts written in karate, safal. This takes two arguments as input, platform name and bat file location of the respective platform
getorchestrationreports action converts the karate all other framework reports into Avo Assure reports and vice versa. This action takes two arguments, reports file path(mandatory) and wait time out(optional)
If invoke platform or get orchestration report, any of the action fails then the appropriate defect will be logged in Jira
JIRA/
Zephyr Scale
Instead of fetching all test cases by default, we provide two filtering options: Priority and Folder Path. Users can either select a specific priority level or enter a folder path to retrieve only the test cases that match the selected criteria. This approach ensures more efficient data retrieval and better relevance in test case management.
Bug Fixes and Improvements:
Refer to the table below to learn more about the bugs addressed along with the respective benefits.
Avo does not support the validation of a pdf which opens in a new browser instance
Avo Assure now allows user to read and validate the content of the PDF which opens in the new tab during debug or execution.
Incorrect pass % of execution reports, showing 100% even though few of the Test Steps are failed.
Incorrect percentage was showing in the reports, this issue is now resolved with the enhancement below:
For any test report if pass percentage is below 99% then it should display rounded number for both pass and fail.
If it is above 99%, Then the decimals of the pass/failure percentage should be displayed in reports.
Keyword to get the row count from the UI table based on column name
With this enhancement, User is able to fetch the occurrence of a text from the specified column of a grid/table.
No Browser type and machine name is mentioned in any of the reports like email report, pdf, summary etc.
This issue has been resolved with current enhancements:
Browser type is visible in the reports as to know from which browser this execution is performed.
Machine name is also visible in the reports to know from which machine/by which user the execution is performed. As to get additional details like screenshots of the executed TC etc.
Browser/client name is visible in all the reports format like HTML, PDF, PDF detailed and in the email, notification reports (attachment)
Subject of the Email does not show Project name and Execution List Name
This issue has been resolved with current enhancements:
Subject of email will include Project name and Execution List name
Format should be (Project Name- Execution list Name – Execution Completed)
Get Row and Column action was giving row number and column name as output
This issue has been resolved with current enhancements and now, this action is displaying row number and column number as output.
Debug/Execution is not working properly.
This issue has been resolved,
If the notification given debug is in progress, the execution will start on console and browser will be launched.
Previous Release Items
Note: Previous release also included below fixes (These items were demonstrated on 6th May)
Multi-browser execution is not working; the execution is happening only on the first selected browser
The issue has been resolved. Users can now select a single browser, and the execution will occur on that specific browser.
Rerun option was not working as expected for all failed Test Cases
When we apply on-failure option as re-run, then the re-run for failed Test Cases happens only for the first failed test case and following that if any other test is failed it doesn't re-run.
This issue is now resolved, and rerun is working as expected for all the failed Test Cases.
Recovery Steps are getting executed only for the first failed Test Case
When we apply on-failure option as re-run/run next Test Case, then the recovery steps are getting executed only for the first failed Test Case and following that if any other test is failed Recovery Steps are not getting executed.
This issue is now fixed, and Recovery Step is working for all failed Test Cases.
Run next testcase is working only for the first failed Test Case
When we apply on-failure option as run next Test Case, then the steps after the failed step get skipped only for the first failed test case.
This issue is now fixed, and run next testcase is working for all failed Test Cases.
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.2.1 enhance your experience with the platform
Last updated
Was this helpful?