Discover What’s New in algoQA v5.0.17 |
|---|
![]() |
Enhancements- algoScraper Improvements
Enhanced Desktop Automation by introducing a Desktop Scraper for the WinAppDriver framework. The new scraper allows users to scrape all UI elements or individual elements and record user actions in real time as they are performed, simplifying desktop automation. To know more click here.
Enhanced M-App Scraper by improving token management and user profile handling. The scraper now prompts for a token only during the initial connection and automatically reconnects using the saved token on subsequent launches. Users can update the token using the Change Token option, switch between different user profiles when required, and are prompted to enter a new valid token if the saved token expires. To know more click here.
Enhanced algoScraper by improving verification action mapping based on captured control types. The scraper now automatically maps controls to the appropriate verification actions, such as Verify Checked/Unchecked, Verify Displayed, or Verify Text. Additionally, when verifying Textbox, Textarea, or Dropdown List controls with unavailable control values, users can use the Avoid Param option in Test Step Settings to ensure successful script generation and execution. To know more click here.
- Test Design Improvements
Users can now merge scenarios from the Scenario List in the exact order they are selected. The merged scenario preserves the selected sequence, ensuring the steps are combined accordingly (for example, selecting scenarios in the order 4 → 2 → 3 merges the steps in the same order). To know more click here.
Enhanced Test Design by allowing multiple alias steps for the same control. Users can now create multiple alias steps for the same control and action by using different parameter values while retaining the same alias step text. Additionally, multiple alias steps can be created for the same control by assigning different actions (default or custom). Duplicate alias steps with the same control, action, and parameter values are prevented, regardless of the GWT prefix or GWT line. To know more click here.
Enhanced Test Design by adding additional Review Status options to the Scenario List table. Users can now filter scenarios using the newly added review statuses: Not Reviewed, Peer Reviewed with Comments, Peer Comments Fixed, Peer Accepted, QA Reviewed with Comments, QA Comments Fixed, QA Accepted, Need Discussion, and On Hold. To know more click here.
- Scripts and Reports Improvements
Enhanced Web Automation for the Python Selenium framework by improving Soft Assertions. When Soft Assertion is enabled in the application settings, test execution continues even if individual steps fail. After execution, all failed steps are clearly highlighted with an "Assertion Failed" message in both the HTML and PDF reports. To know more click here.
Enhanced Web Automation for the Java Selenium framework by introducing built-in Auto Scroll, Auto Wait, and Wait Optimization during execution. The framework automatically scrolls elements into view, waits until elements are visible and ready for interaction, and proceeds as soon as elements become available within the configured timeout, eliminating the need for custom actions or explicit wait steps while improving execution performance To know more click here.
- Dashboard Improvements
Enhanced Web Automation by adding Dashboard support for the JavaScript Selenium framework, enabling users to monitor execution details and view automation insights directly from the dashboard. To know more click here.
Enhanced Web Automation for the JavaScript Selenium framework by adding Smart Ordering support, enabling automatic ordering of test cases. To know more click here.
- algoQA Improvements
Enhanced algoQA by redesigning the ticket submission form with additional fields, including Issue Title, Issue Description, Reproduction Steps, Expected Results, Priority, and Supporting Documents, enabling users to provide complete issue details. Users can now raise Issues, Enhancement Requests, New Feature Requests, or request a Support Session. To know more click here.
Enhanced algoQA by adding support for uploading multiple images while creating a project, allowing users to create an offline model and generate test scripts by uploading multiple screenshots while creating project or in existing project. To know more click here.
Enhanced algoQA by adding support for creating nested folder structures when generating separate feature files. Users can now use the forward slash (/) within folder structure to automatically create nested folders in the Test Cases folder. To know more click here.
- Object Repository Improvements
Enhanced Object Repository by replacing CSV import support with JSON format for uploading scraped files while mapping locators, providing a more streamlined and standardized import process. To know more click here.
- Smart Report Analysis Improvements
Enhanced Smart Report Analysis by including the failure reason and the last captured screenshot for failed test cases, clearly highlighting the exact point of failure to simplify root cause analysis and debugging. To know more click here.
- Desktop Automation Improvements
Enhanced Desktop Automation by setting Click by Index as the default action for the Python TestComplete framework, improving interaction with controls that contain multiple matching elements. To know more click here.
Enhanced Desktop Automation for the Python TestComplete framework by preventing images from being added automatically to the ImageRepository folder in TestComplete. If required, users can manually upload images through Customize Script by navigating to Image Repo and using the Upload File option. To know more click here.
Enhanced Desktop Automation for the C# WinAppDriver framework by adding support for merging multiple steps into a single step, simplifying test cases and improving their readability and maintainability. To know more click here.
Enhanced Desktop Automation for the C# WinAppDriver framework by automatically adding the corresponding assertion to the step definition when a custom action name begins with "Verify", simplifying the creation of verification steps. To know more click here.
Enhanced Desktop Automation by introducing a Desktop Scraper for the WinAppDriver framework. The new scraper allows users to scrape all UI elements or individual elements and record user actions in real time as they are performed, simplifying desktop automation. To know more click here.
Enhanced M-App Scraper by improving token management and user profile handling. The scraper now prompts for a token only during the initial connection and automatically reconnects using the saved token on subsequent launches. Users can update the token using the Change Token option, switch between different user profiles when required, and are prompted to enter a new valid token if the saved token expires. To know more click here.
Enhanced algoScraper by improving verification action mapping based on captured control types. The scraper now automatically maps controls to the appropriate verification actions, such as Verify Checked/Unchecked, Verify Displayed, or Verify Text. Additionally, when verifying Textbox, Textarea, or Dropdown List controls with unavailable control values, users can use the Avoid Param option in Test Step Settings to ensure successful script generation and execution. To know more click here.
Users can now merge scenarios from the Scenario List in the exact order they are selected. The merged scenario preserves the selected sequence, ensuring the steps are combined accordingly (for example, selecting scenarios in the order 4 → 2 → 3 merges the steps in the same order). To know more click here.
Enhanced Test Design by allowing multiple alias steps for the same control. Users can now create multiple alias steps for the same control and action by using different parameter values while retaining the same alias step text. Additionally, multiple alias steps can be created for the same control by assigning different actions (default or custom). Duplicate alias steps with the same control, action, and parameter values are prevented, regardless of the GWT prefix or GWT line. To know more click here.
Enhanced Test Design by adding additional Review Status options to the Scenario List table. Users can now filter scenarios using the newly added review statuses: Not Reviewed, Peer Reviewed with Comments, Peer Comments Fixed, Peer Accepted, QA Reviewed with Comments, QA Comments Fixed, QA Accepted, Need Discussion, and On Hold. To know more click here.
Enhanced Web Automation for the Python Selenium framework by improving Soft Assertions. When Soft Assertion is enabled in the application settings, test execution continues even if individual steps fail. After execution, all failed steps are clearly highlighted with an "Assertion Failed" message in both the HTML and PDF reports. To know more click here.
Enhanced Web Automation for the Java Selenium framework by introducing built-in Auto Scroll, Auto Wait, and Wait Optimization during execution. The framework automatically scrolls elements into view, waits until elements are visible and ready for interaction, and proceeds as soon as elements become available within the configured timeout, eliminating the need for custom actions or explicit wait steps while improving execution performance To know more click here.
Enhanced Web Automation by adding Dashboard support for the JavaScript Selenium framework, enabling users to monitor execution details and view automation insights directly from the dashboard. To know more click here.
Enhanced Web Automation for the JavaScript Selenium framework by adding Smart Ordering support, enabling automatic ordering of test cases. To know more click here.
Enhanced algoQA by redesigning the ticket submission form with additional fields, including Issue Title, Issue Description, Reproduction Steps, Expected Results, Priority, and Supporting Documents, enabling users to provide complete issue details. Users can now raise Issues, Enhancement Requests, New Feature Requests, or request a Support Session. To know more click here.
Enhanced algoQA by adding support for uploading multiple images while creating a project, allowing users to create an offline model and generate test scripts by uploading multiple screenshots while creating project or in existing project. To know more click here.
Enhanced algoQA by adding support for creating nested folder structures when generating separate feature files. Users can now use the forward slash (/) within folder structure to automatically create nested folders in the Test Cases folder. To know more click here.
Enhanced Object Repository by replacing CSV import support with JSON format for uploading scraped files while mapping locators, providing a more streamlined and standardized import process. To know more click here.
Enhanced Smart Report Analysis by including the failure reason and the last captured screenshot for failed test cases, clearly highlighting the exact point of failure to simplify root cause analysis and debugging. To know more click here.
Enhanced Desktop Automation by setting Click by Index as the default action for the Python TestComplete framework, improving interaction with controls that contain multiple matching elements. To know more click here.
Enhanced Desktop Automation for the Python TestComplete framework by preventing images from being added automatically to the ImageRepository folder in TestComplete. If required, users can manually upload images through Customize Script by navigating to Image Repo and using the Upload File option. To know more click here.
Enhanced Desktop Automation for the C# WinAppDriver framework by adding support for merging multiple steps into a single step, simplifying test cases and improving their readability and maintainability. To know more click here.
Enhanced Desktop Automation for the C# WinAppDriver framework by automatically adding the corresponding assertion to the step definition when a custom action name begins with "Verify", simplifying the creation of verification steps. 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
