See what’s new in our product release notes version: new features, enhancements & bug fixes for algoQA V5.0.8 |
|---|
 |
Enhancements- API Automation Improvements
Added the ability to import API collections in both .json and .xlsx formats and introduced the option to create a new API collection via ‘Save As’. Clicking the ‘+’ icon allows users to enter a collection name, after which the collection is created, selected, and the Save button is enabled. Added None as a supported request body format. In the API Generate Script screen, once a collection is selected, the Selected Request List is now chosen by default. A search field has been added to quickly locate environment variables, which can also be downloaded using the file naming format: projectName_EnvironmentVariables. Environment Variable Permissions have been added in access settings, allowing admins to grant users the ability to Add, Edit, and Delete environment variables within an API project. Validation has been implemented to prevent the use of special characters (*, $, ^, ,, +, >, ?, |, (, ), {, <, [, ]) when creating a separate feature file. Additionally, in API automation, IDs for each API, which were previously generated in the env.json file, are now generated directly in the feature file. To know more click here.
- Enhanced Validation to Prevent Duplicate Naming
Restricted case-sensitive variations of the same name to prevent duplicate entries. For example, names such as Home page, Home_page, Homepage, homepage, home page, home_page, HOME PAGE, and HOME_page are now treated as duplicates and cannot be created separately. To know more click here.
- Introducing Scenario History
Users can now view the history of a scenario by clicking the Scenario History icon from the Scenario Steps List or Scenarios List. The history shows all actions performed, who performed them, and the date and time. Users can search logs and apply filters by time (Today, One Week, Custom) and log type (All, Success, Info, Error) by clicking Apply. To know more click here.
- Unified Method Name Update for Custom Actions
Added support for defining multiple actions with the same method name. To know more click here.
- Added Load-Testing Support to AlgoQA
Enhanced algoQA by adding the ability to perform load testing. To know more click here.
- Introduced cross-platform execution for automation scripts
In Web automation and python selenium framework, added the ability to execute scripts in ubuntu and redhat. To know more click here.
- Auto-Healing Improvements
Enhanced auto-healing by introducing a new <CaptureXpathAndTarget> tag in the application settings file, resulting in significantly reduced script execution time. To know more click here.
- Expanded XPath Compatibility (iframe + Shadow DOM)
Enhanced script execution by adding support for both iframe XPaths and Shadow DOM XPaths. To know more click here.
- Dashboard Enhancements
Enhanced the dashboard with Failure Trends Over Time by suites, multiple graph views for Test Severity Distribution and Test Health Score Distribution, a customizable range selector for user-defined graphs, and an improved Test Health Summary table with better navigation and layout. To know more click here.
- Feature File Quality Analyzer Enhancements
Enhanced the Feature File Quality Analyzer by adding a Comments section in the Detailed Suggestions table, allowing users to identify the specific lines to review, and updated the category levels to Warning and Critical for a more robust view. To know more click here.
Added the ability to import API collections in both .json and .xlsx formats and introduced the option to create a new API collection via ‘Save As’. Clicking the ‘+’ icon allows users to enter a collection name, after which the collection is created, selected, and the Save button is enabled. Added None as a supported request body format. In the API Generate Script screen, once a collection is selected, the Selected Request List is now chosen by default. A search field has been added to quickly locate environment variables, which can also be downloaded using the file naming format: projectName_EnvironmentVariables. Environment Variable Permissions have been added in access settings, allowing admins to grant users the ability to Add, Edit, and Delete environment variables within an API project. Validation has been implemented to prevent the use of special characters (*, $, ^, ,, +, >, ?, |, (, ), {, <, [, ]) when creating a separate feature file. Additionally, in API automation, IDs for each API, which were previously generated in the env.json file, are now generated directly in the feature file. To know more click here.
Restricted case-sensitive variations of the same name to prevent duplicate entries. For example, names such as Home page, Home_page, Homepage, homepage, home page, home_page, HOME PAGE, and HOME_page are now treated as duplicates and cannot be created separately. To know more click here.
Users can now view the history of a scenario by clicking the Scenario History icon from the Scenario Steps List or Scenarios List. The history shows all actions performed, who performed them, and the date and time. Users can search logs and apply filters by time (Today, One Week, Custom) and log type (All, Success, Info, Error) by clicking Apply. To know more click here.
Added support for defining multiple actions with the same method name. To know more click here.
Enhanced algoQA by adding the ability to perform load testing. To know more click here.
In Web automation and python selenium framework, added the ability to execute scripts in ubuntu and redhat. To know more click here.
Enhanced auto-healing by introducing a new <CaptureXpathAndTarget> tag in the application settings file, resulting in significantly reduced script execution time. To know more click here.
Enhanced script execution by adding support for both iframe XPaths and Shadow DOM XPaths. To know more click here.
Enhanced the dashboard with Failure Trends Over Time by suites, multiple graph views for Test Severity Distribution and Test Health Score Distribution, a customizable range selector for user-defined graphs, and an improved Test Health Summary table with better navigation and layout. To know more click here.
Enhanced the Feature File Quality Analyzer by adding a Comments section in the Detailed Suggestions table, allowing users to identify the specific lines to review, and updated the category levels to Warning and Critical for a more robust view. To know more click here.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article