See what’s new in our product release notes version: new features, enhancements & bug fixes for algoQA V5.0.5 |
|---|
 |
Enhancements- SSO Improvements
When an account is accessed from a different system, users will now be notified of an existing active session. If the user chooses to continue, the previous session will be logged out, and the new session will become active. Additionally, a notification email will be sent to the owner of the account with the login details, prompting the user to review the activity if it was not initiated by them. To know more for freemium users click here, Pro users click here and Enterprise users click here.
- Create Project Page Improvements
Enhanced algoScraper by enabling direct launch from algoQA. For Web & M-Site, enter the application URL and click Launch to open the scraper in that URL, for M-App, no URL is needed and the scraper can be launched directly, with an optional token for local authentication, if algoScraper is missing or outdated, a pop-up will prompt to download the latest version. This feature supports both web and mobile automation. For existing project user can launch the scraper from upload scraped file, scrape the UI elements and upload the scraped file. To know more click here.
- Scraper Improvements
Enhanced algoScraper by providing Error Message, if user click on "start recording" button without adding scenario name and scenario outline, Provided an option to edit in Record Scenario page by clicking on eye icon, Provided a pop-up notification after downloading scraped file saying File downloaded successfully, While recording a scenario if user clicks on Close icon, a warning message will be displayed saying Closing now will erase all your saved actions. This cannot be undone, click on Yes Close if you wish to close or click on cancel. To know more click here.
- Merge Multiple Steps and alias step Improvements
Enhanced Merge Multiple Steps to one by providing auto suggestions while creating custom method for File name, action name, method name, description, get alias step auto created and while using existing method for method name, enhancing usability and efficiency. To know more click here.
- Alias Name Improvements
algoQA now prevents users from creating Alias Names that match existing Control Names within the same feature, if users try to use it an error message will be displayed saying Can't add Alias Name similar to Control Name, try with some other name. Alias Names already used by other controls appear disabled with an error message saying: You can't use this alias name as it belongs to another control. To know more click here.
- View Logs Improvements
Enhanced View Logs by displaying user-specific activities and have updated categories according to the V5 specifications. To know more click here.
- Email Report Alert Improvements
Enhanced Email Reports by removing failure summary when there is no failure in execution and attach failure summary when there is a failure with failure reason. To know more click here.
- Report Improvements
In the Web Automation and Python Selenium framework, you will have an option to generate feature file-wise PDF reports when executing multiple feature files in a single batch, in addition to the consolidated PDF report. After execution, there will be individual PDF reports for each feature file. These reports are stored in:
TestReports>>FeatureWiseReports. To know more click here.
In the Web Automation and Python Selenium framework, you will have an option to have screenshot with date and time in report, In the application settings file, set <EnableFullScreenshot> to True to get Full screenshots in report.
In the reports, (HTML, PDF, Allure), the screenshots will be captured with the application URL, taskbar with date and time. To know more click here.
- Script Improvements
In the Web Automation and Java Selenium, C# Selenium framework, enhanced the script by removing the webdriver path from the script so that the size of the script is reduced, In Application settings file <WebdriverPath>Na</WebdriverPath> is replaced with <EnableWebdriverPath>True</EnableWebdriverPath>. If this tag is set True, Users have to provide the webdriver in the resources folder in scripts. If the tag is set False, webdriver will be installed during execution.
- BDD Quality Analyzer Improvements
Enhanced the BDD Quality Analyzer report to include a detailed summary with numbers and percentages of test cases categorized as Well Defined, Needs Work, or Requires Revision based on Given-When-Then (GWT) steps, accompanied by a pie chart for visual clarity. Added a Detailed Suggestions table listing Scenario Name, Test ID, Category (Major or Minor), and specific improvement recommendations, each identified by a unique number, it can be from 1 to 9 based on the size of the test cases. To know more click here.
- Auto Healing Improvements
Auto-healing functionality has been implemented for custom action XPaths in the Web Automation Java Selenium framework. To support this, the CommonUtil.storeElementInJson(output, elementHtml); call has been removed from individual functions and workflows. Element locator and target capture is now centralized within the getYMLObjectRepositoryData() method, enabling consistent tracking, including for custom methods. Action Required: Developers must update custom method definitions to include an additional identification parameter, which must be passed to getYMLObjectRepositoryData() to ensure proper capture in htmlElement.json.
Bug Fixes
- Scraper issues
In algoScraper, If the user adds multiple scenarios without specifying scenario names, the data from the second scenario does not appear after downloading and appending it into algoQA. A code fix has been implemented to ensure that this issue doesn't occur again.
When an account is accessed from a different system, users will now be notified of an existing active session. If the user chooses to continue, the previous session will be logged out, and the new session will become active. Additionally, a notification email will be sent to the owner of the account with the login details, prompting the user to review the activity if it was not initiated by them. To know more for freemium users click here, Pro users click here and Enterprise users click here.
Enhanced algoScraper by enabling direct launch from algoQA. For Web & M-Site, enter the application URL and click Launch to open the scraper in that URL, for M-App, no URL is needed and the scraper can be launched directly, with an optional token for local authentication, if algoScraper is missing or outdated, a pop-up will prompt to download the latest version. This feature supports both web and mobile automation. For existing project user can launch the scraper from upload scraped file, scrape the UI elements and upload the scraped file. To know more click here.
Enhanced algoScraper by providing Error Message, if user click on "start recording" button without adding scenario name and scenario outline, Provided an option to edit in Record Scenario page by clicking on eye icon, Provided a pop-up notification after downloading scraped file saying File downloaded successfully, While recording a scenario if user clicks on Close icon, a warning message will be displayed saying Closing now will erase all your saved actions. This cannot be undone, click on Yes Close if you wish to close or click on cancel. To know more click here.
Enhanced Merge Multiple Steps to one by providing auto suggestions while creating custom method for File name, action name, method name, description, get alias step auto created and while using existing method for method name, enhancing usability and efficiency. To know more click here.
algoQA now prevents users from creating Alias Names that match existing Control Names within the same feature, if users try to use it an error message will be displayed saying Can't add Alias Name similar to Control Name, try with some other name. Alias Names already used by other controls appear disabled with an error message saying: You can't use this alias name as it belongs to another control. To know more click here.
Enhanced View Logs by displaying user-specific activities and have updated categories according to the V5 specifications. To know more click here.
Enhanced Email Reports by removing failure summary when there is no failure in execution and attach failure summary when there is a failure with failure reason. To know more click here.
In the Web Automation and Python Selenium framework, you will have an option to generate feature file-wise PDF reports when executing multiple feature files in a single batch, in addition to the consolidated PDF report. After execution, there will be individual PDF reports for each feature file. These reports are stored in:
TestReports>>FeatureWiseReports. To know more click here.
In the Web Automation and Python Selenium framework, you will have an option to have screenshot with date and time in report, In the application settings file, set <EnableFullScreenshot> to True to get Full screenshots in report.
In the reports, (HTML, PDF, Allure), the screenshots will be captured with the application URL, taskbar with date and time. To know more click here.
In the Web Automation and Java Selenium, C# Selenium framework, enhanced the script by removing the webdriver path from the script so that the size of the script is reduced, In Application settings file <WebdriverPath>Na</WebdriverPath> is replaced with <EnableWebdriverPath>True</EnableWebdriverPath>. If this tag is set True, Users have to provide the webdriver in the resources folder in scripts. If the tag is set False, webdriver will be installed during execution.
Enhanced the BDD Quality Analyzer report to include a detailed summary with numbers and percentages of test cases categorized as Well Defined, Needs Work, or Requires Revision based on Given-When-Then (GWT) steps, accompanied by a pie chart for visual clarity. Added a Detailed Suggestions table listing Scenario Name, Test ID, Category (Major or Minor), and specific improvement recommendations, each identified by a unique number, it can be from 1 to 9 based on the size of the test cases. To know more click here.
Auto-healing functionality has been implemented for custom action XPaths in the Web Automation Java Selenium framework. To support this, the CommonUtil.storeElementInJson(output, elementHtml); call has been removed from individual functions and workflows. Element locator and target capture is now centralized within the getYMLObjectRepositoryData() method, enabling consistent tracking, including for custom methods. Action Required: Developers must update custom method definitions to include an additional identification parameter, which must be passed to getYMLObjectRepositoryData() to ensure proper capture in htmlElement.json.
Bug FixesIn algoScraper, If the user adds multiple scenarios without specifying scenario names, the data from the second scenario does not appear after downloading and appending it into algoQA. A code fix has been implemented to ensure that this issue doesn't occur again.
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