Applies to algoQA V4.5
- The Response body Issue
In API automation, for a particular API, the response body was not appearing while the status code was present. A code fix has been implemented to ensure that both the response body and status code are displayed. - algoAF Script Issue
In algoAF Script, while uploading the JAR file, an error message appeared indicating an issue during virus scanning . Now, the virus scanning of JAR file is skipped, so the error message is no longer displayed. - Auto-healing Functionality Issue
The auto-healing functionality was inconsistent without scraped file, as it was not selecting correct Xpath. A code fix has been implemented to ensure the auto-healing functionality works properly without the scraped file. - Scripts Issue
Earlier user's used to create same Alias step with different GWT prefix and duplicate implementation was created. Now user's can use Different GWT prefix for same alias steps and it will create only one GWT line to avoid duplicate implementation in script. - Feature File Issue
In Feature file, While generating test cases from separate feature file the test count of test cases generated was wrong. A code fix has been implemented to ensure test case generation works properly.
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