See what’s new in our product release notes version: new features, enhancements & bug fixes for algoQA V4.4.6 |
|---|
 |
Enhancements- Azure DevOps Server Integration
Azure DevOps Server, previously known as Team Foundation Server (TFS) and Visual Studio Team System (VSTS), provides tools for software development and project management. This release introduces functionality for creating issues and identifying any duplicate issues within Azure DevOps. For more information, see Azure DevOps Server (Team Foundation Server) Integration. - New Feature update: Create Project Directly from algoScraper extension.
This release introduces a new feature that allows you to create a project directly from the algoScraper extension. This feature eliminates the need to manually download scraped files from algoScraper and upload them again for creating an offline model. For more information, see How to Create a Project using algoScraper Extension.
User Storage Enhancement
In a centralized project, previously only administrators had the ability to delete test cases stored in the system. Upon receiving the message - "storage is full", users had to contact administrators for assistance in managing the storage.
This functionality has been enhanced so that users can delete the test data stored.
- Dashboard Improvements
In the Dashboard screen, Batch ID is introduced in the Batch Execution Summary section. which is a unique identifier for the reports that are generated. For more information, see Dashboard.
- Edit Scenario Improvements
In the Scenario Sequence section, you can now use the keyword (_empty_) to use blank spaces in custom value and Message text boxes, otherwise error message is displayed. For more information, see Edit Scenario Secondary Screen View and Toolbars. - UI Improvements
The look and feel of the Main Canvas screen and navigation bar are enhanced to improve the user experience. For more information, refer to Toolbars and Views within algoQA Platform .
- Subscription Page enhancement
In the subscription page, in a centralized project, previously only administrators had the ability to delete test data stored in the system. Upon receiving the message - "storage is full", users had to contact administrators for assistance in managing the storage.
This functionality has been enhanced so that users can delete the test data stored without needing to contact administrators.
To access Subscription page- Navigate to the Main canvas after logging into algoQA > user profile picture or name > My Subscription.
- Web Actions Update
The "Copied Text by Key" default action has been enhanced to include key-value pair information in the generated report. When text is copied using this action, both the key (identifier) and the value (copied text) will now be printed in the report in the following format:
key: value.
For more information, see Copied Text by Key Action.
- Create Project Page Improvements
- Project Name field now requires a minimum of 2 characters.
"Application Type" dropdown has been renamed to "Automation Type"
- API Test Automation Improvements
A new negative verification has been implemented to check for 403 Forbidden status in the API automation tests.
A fix has been applied to properly handle parameters containing "na". The automation now correctly stores the response variable when such parameters are included in the request.
For example, parameters Parameters such as name=na are correctly processed, and the response variable is successfully stored.
For more information, refer to API Test Automation article
Azure DevOps Server, previously known as Team Foundation Server (TFS) and Visual Studio Team System (VSTS), provides tools for software development and project management. This release introduces functionality for creating issues and identifying any duplicate issues within Azure DevOps. For more information, see Azure DevOps Server (Team Foundation Server) Integration.
This release introduces a new feature that allows you to create a project directly from the algoScraper extension. This feature eliminates the need to manually download scraped files from algoScraper and upload them again for creating an offline model. For more information, see How to Create a Project using algoScraper Extension.
User Storage Enhancement
In a centralized project, previously only administrators had the ability to delete test cases stored in the system. Upon receiving the message - "storage is full", users had to contact administrators for assistance in managing the storage.
This functionality has been enhanced so that users can delete the test data stored.
In the Dashboard screen, Batch ID is introduced in the Batch Execution Summary section. which is a unique identifier for the reports that are generated. For more information, see Dashboard.
In the Scenario Sequence section, you can now use the keyword (_empty_) to use blank spaces in custom value and Message text boxes, otherwise error message is displayed. For more information, see Edit Scenario Secondary Screen View and Toolbars.
The look and feel of the Main Canvas screen and navigation bar are enhanced to improve the user experience. For more information, refer to Toolbars and Views within algoQA Platform .
In the subscription page, in a centralized project, previously only administrators had the ability to delete test data stored in the system. Upon receiving the message - "storage is full", users had to contact administrators for assistance in managing the storage.
This functionality has been enhanced so that users can delete the test data stored without needing to contact administrators.
To access Subscription page- Navigate to the Main canvas after logging into algoQA > user profile picture or name > My Subscription.
The "Copied Text by Key" default action has been enhanced to include key-value pair information in the generated report. When text is copied using this action, both the key (identifier) and the value (copied text) will now be printed in the report in the following format:
key: value.
For more information, see Copied Text by Key Action.
- Project Name field now requires a minimum of 2 characters.
"Application Type" dropdown has been renamed to "Automation Type"
A new negative verification has been implemented to check for 403 Forbidden status in the API automation tests.
A fix has been applied to properly handle parameters containing
"na". The automation now correctly stores the response variable when such parameters are included in the request. For example, parameters Parameters such as name=na are correctly processed, and the response variable is successfully stored.
For more information, refer to API Test Automation article
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