Release Notes V5.0.3

Modified on Mon, 1 Sep at 3:21 PM


See what’s new in our product release notes version: new features, enhancements & bug fixes for algoQA V5.0.3

Enhancements
  • Test Design Improvements
    Introduced filter options in the Scenario List for separate Feature and Folder structure. These filters are now also available in Scenario Search.

  • Auto Suggestions to Re-Use Alias Step Improvements
    Enhanced alias step reuse with auto-suggestion and intelligent field population when selecting or typing an alias step, related fields like Control, Feature, and Action are auto-filled and locked where applicable; the system now auto-detects alias steps based on selected controls, clears alias on control removal, and restricts manual edits to action fields mapped via alias steps with inline warnings.

  • Scraper Improvements
    Updated the scenario recording logic by making the 'Scenario Name' field optional and setting the 'Scenario Outline' field as mandatory. Steps are now grouped using refined logic, enabling more accurate and flexible scenario organization during recording.
    While recording a scenario in Scraper, the page name had to be added manually. We've now enhanced the feature so that the page name is updated automatically.



     Bug Fixes


  • Script Generation issues

    Resolved an issue in the Web Automation and Java Selenium framework where test scripts were failing in headless mode due to a small default window size. Implemented a code fix to set an appropriate window resolution, ensuring consistent and reliable execution. 

    Resolved an issue in AlgoQA where simultaneous script generation by multiple users on a centralized project caused the process to hang with a persistent loading screen. A code fix has been implemented to ensure smooth and uninterrupted script generation in such scenarios.


  • Data Decoupling issues

    Fixed an issue where, upon generating test cases with data decoupling enabled, the downloaded Excel data set displayed only key values from the feature/txt file instead of the corresponding default values defined in the YAML file. The Excel now doesn't shows default values aswell, ensuring clarity and accuracy in the data set.


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article