Release Notes - Assure v26.1.3
Avo is excited to announce the release of new version 26.1.3. Here are the enhancements:
Key Enhancements
Enhanced Import Functionality in Test Data Management
Test Data Management ignores empty rows and columns during import and does not include them in the Data Table, ensuring cleaner and more accurate data. Learn more
Improved Handling of Swagger/OpenAPI 3.x Imports
Enabled OpenAPI 3.x import (via file &JSON) to seamlessly parse and onboard API definitions, improving compatibility with modern API specifications. Learn more
Improved JSON Data Visibility During Drag-and-Drop in Test Case
Enhanced JSON handling in Test cases to fully support arrays and nested structures, ensuring all values are correctly populated during drag-and-drop from the Element Repository. Also enabled selection of array keys and support for passing dynamic and static values at the test case level. Learn more
Support for PATCH Method in API Testing
You can now use the PATCH method in API testing to update specific parts of a resource. The Avo Assure allows you to configure PATCH requests with headers and request bodies (JSON or XML), execute them, and validate responses. PATCH APIs are also supported during Swagger/OpenAPI import and can be used in Test cases for response validation and data handling, just like other API methods. Learn more
Bug Fixes and Improvements
See the following table for the bugs resolved and the key benefits.
Fixed Issue with Large Screenshots in Element Repository
After capturing elements, large screenshots were displayed instead of the actual size in View Screenshot. This issue is resolved, and screenshots now display the correct size.
Fixed Issue with Test Step Group Order During Debug
Debugging a Test case that contained multiple Test Step Groups did not follow the original Test Step Group design order and instead executed based on the order of checkbox selection in the Debug popup. This issue is resolved, and debugging now follows the original Test Step Group design order.
Fixed Issue with Element dropdown Closing After Each Edit
The Element dropdown closed after each edit when manually creating an element, requiring users to scroll and reopen it repeatedly. This issue is resolved, and the dropdown now remains open during edits for smoother interaction.
Fixed Issue with Step Options Not Visible in Last Test Step Group
After adding multiple Test Step Groups in a Test case, selecting the + icon in the last Test Step Group displayed step options that were partially hidden, preventing proper selection. This issue is resolved, and the Add Step options now display completely and can be selected without issues.
Fixed Issue with Wait for Element to be Visible Action
The Wait for Element to Be Visible action failed when a manually created element was used in the test steps. This issue is resolved, and the action now works correctly with manually created elements.
Fixed Issues After Migration of Selenium to Avo
The data-el-id was not stored in the Element Repository. This issue is resolved, and the data-el-id is now stored correctly.
All projects were not appearing in the project selection dropdown. This issue is resolved, and all projects now display correctly.
The output folder for selenium_testcase_batch.zip (JSON files) was not persistent and was overridden on each run. This issue is resolved, and the output folder now retains previous run artifacts.
Improper element naming occurred when duplicate elements existed. This issue is resolved, and element naming now follows a proper convention.
Duplicate elements were created across multiple imports. This issue is resolved, and duplicate element creation is now prevented.
Fixed Issue with Personal Access Token checkbox Not Retained in Versioning Tab
The Personal Access Token (PAT) checkbox in the Versioning tab did not retain its selected state after navigation. This issue is resolved, and the checkbox selection now retains as expected.
Fixed Issue with Missing Screenshots in Reports
Executing Test cases from the Execution List did not display screenshots in the HTML and PDF with screenshots reports. This issue is resolved, and screenshots now appear correctly in both HTML and PDF with screenshots reports.
Last updated
Was this helpful?