See what’s new in our product release notes version: new features, enhancements & bug fixes for algoQA V4.5.1 |
|---|
 |
Enhancements- Auto-healing Improvements
In Script generation, Auto-healing is now available for Python Selenium framework.
- algoScraper Improvements
In algoScraper, Now custom method support is available for feature file to script conversion, to access this navigate to algoScraper>More.
After recording a custom action and downloading, the utility file was downloaded multiple times but now with a configuration changes it is downloading single time.
Webdriver io Improvements
Enhanced the automation framework to interact with elements inside shadow dom, which are usually hidden from standard DOM queries.
Improved support for lazy loaded pages, ensuring that the automation waits for elements to fully load before interacting with them.
Integrated API calls (GET, POST, PATCH) into the test framework to validate backend responses and set up test data efficiently.
- Auto Mapping Improvements
Enhancement for Auto mapping of custom action to default method. while uploading the scraped file, users used to check the existing scenario steps default action based on the same control name, now this is can be auto mapped it with custom action.
Mapping of input feature file steps with algoQA feature file were not being created using auto-mapping, with some configuration changes the response now will have the mapping of input feature file steps and intermediate steps created by LLM.
- Feature File Improvements
Currently algoQA has default given steps in beginning and end of the scenarios , to avoid the default steps, while a user enters the Alias step, test step setting field would be enabled and user must enter No precondition and no post condition to avoid default steps in scenarios.
In the execution report, steps were shown from input feature file instead of steps from algoQA feature file, now with some configuration changes steps will be shown from algoQA feature file.
- Utility File Improvements
In Utility files, while creating more than 1 utility file only 1 import statement was been created now with some configuration changes all import statements are present in the workflow.
While performing centralized testing in utility file, if admin generates script the lock file was created with the user name with some configuration changes now this is not creating in common folder.
- Custom Action Improvements
In algoScraper, After Recording custom action the Test data was not being fetched in the custom methods after generating script, this has been fixed with some configuration changes.
After creating custom action and uploading the utility file in project, the custom Utility pages were not created after generating script, this has been fixed with some configuration changes.
In Script generation, Auto-healing is now available for Python Selenium framework.
In algoScraper, Now custom method support is available for feature file to script conversion, to access this navigate to algoScraper>More.
After recording a custom action and downloading, the utility file was downloaded multiple times but now with a configuration changes it is downloading single time.
Webdriver io Improvements
Enhanced the automation framework to interact with elements inside shadow dom, which are usually hidden from standard DOM queries.
Improved support for lazy loaded pages, ensuring that the automation waits for elements to fully load before interacting with them.
Integrated API calls (GET, POST, PATCH) into the test framework to validate backend responses and set up test data efficiently.
Enhancement for Auto mapping of custom action to default method. while uploading the scraped file, users used to check the existing scenario steps default action based on the same control name, now this is can be auto mapped it with custom action.
Mapping of input feature file steps with algoQA feature file were not being created using auto-mapping, with some configuration changes the response now will have the mapping of input feature file steps and intermediate steps created by LLM.
Currently algoQA has default given steps in beginning and end of the scenarios , to avoid the default steps, while a user enters the Alias step, test step setting field would be enabled and user must enter No precondition and no post condition to avoid default steps in scenarios.
In the execution report, steps were shown from input feature file instead of steps from algoQA feature file, now with some configuration changes steps will be shown from algoQA feature file.
In Utility files, while creating more than 1 utility file only 1 import statement was been created now with some configuration changes all import statements are present in the workflow.
While performing centralized testing in utility file, if admin generates script the lock file was created with the user name with some configuration changes now this is not creating in common folder.
In algoScraper, After Recording custom action the Test data was not being fetched in the custom methods after generating script, this has been fixed with some configuration changes.
After creating custom action and uploading the utility file in project, the custom Utility pages were not created after generating script, this has been fixed with some configuration changes.
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