See what’s new in our product release notes version: new features, enhancements & bug fixes for algoQA V5.0.3 |
|---|
 |
Enhancements- Warning Message Improvements
Implemented a warning message that prompts users when they attempt to navigate to a different page or URL without saving their current edits. This ensures that users are alerted before losing any unsaved changes.
- Scraper Improvements
The Scenario Name field is no longer mandatory; instead, the Scenario Outline field is now mandatory. Steps are grouped based on a refined logic: if the Scenario Outline is unique, a new scenario is created; if it matches an existing one and the Scenario Name is unique, a new scenario is created using the Scenario Name; if both Scenario Outline and Scenario Name match different existing scenarios, steps are appended to the scenario that matches the Scenario Name, ignoring the outline; and if only the Scenario Name matches, steps are appended to the matching scenario, regardless of the outline. This ensures more accurate and flexible scenario organization during recording.
hile 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 a problem where scripts were failing due to a small default window size in headless mode. A code fix has been implemented to set an appropriate window resolution, ensuring reliable execution.
In python selenium framework, Execution fails with a TypeError when the alias step is invoked with special characters. A code fix has been implemented to ensure that execution doesn't fail with special characters in alias step.
In the Python Selenium framework, while generating scripts, feature wise files were being generated outside the feature folder in algoQA. A code fix has been implemented to ensure that if a feature folder name is provided, a nested folder is correctly created within the specified feature folder.
In the Python Selenium framework, duplicate methods were being created in a workflow during script generation when the same control name, control type, page name, and action were used . A code fix has been implemented to prevent the creation of duplicate methods.
In the Python Selenium framework, while generating scripts, parameters with special cases was mismatching and multiple Parameters were not generating and in report for the param like @copiedtext_1 was coming as it is but that should replace with what @copiedtext_1 contains in report. A code fix as been implemented is implemented to ensure it works as expected.
In the Python Selenium framework, duplicate methods were being created in a workflow during script generation When the same control is used with a custom action and similar alias step multiple times in a workflow, duplicate methods are being generated instead of reusing the existing one. A code fix has been implemented to prevent the creation of duplicate methods.
Implemented a warning message that prompts users when they attempt to navigate to a different page or URL without saving their current edits. This ensures that users are alerted before losing any unsaved changes.
The Scenario Name field is no longer mandatory; instead, the Scenario Outline field is now mandatory. Steps are grouped based on a refined logic: if the Scenario Outline is unique, a new scenario is created; if it matches an existing one and the Scenario Name is unique, a new scenario is created using the Scenario Name; if both Scenario Outline and Scenario Name match different existing scenarios, steps are appended to the scenario that matches the Scenario Name, ignoring the outline; and if only the Scenario Name matches, steps are appended to the matching scenario, regardless of the outline. This ensures more accurate and flexible scenario organization during recording.
hile 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 FixesResolved a problem where scripts were failing due to a small default window size in headless mode. A code fix has been implemented to set an appropriate window resolution, ensuring reliable execution.
In python selenium framework, Execution fails with a TypeError when the alias step is invoked with special characters. A code fix has been implemented to ensure that execution doesn't fail with special characters in alias step.
In the Python Selenium framework, while generating scripts, feature wise files were being generated outside the feature folder in algoQA. A code fix has been implemented to ensure that if a feature folder name is provided, a nested folder is correctly created within the specified feature folder.
In the Python Selenium framework, duplicate methods were being created in a workflow during script generation when the same control name, control type, page name, and action were used . A code fix has been implemented to prevent the creation of duplicate methods.
In the Python Selenium framework, while generating scripts, parameters with special cases was mismatching and multiple Parameters were not generating and in report for the param like @copiedtext_1 was coming as it is but that should replace with what @copiedtext_1 contains in report. A code fix as been implemented is implemented to ensure it works as expected.
In the Python Selenium framework, duplicate methods were being created in a workflow during script generation When the same control is used with a custom action and similar alias step multiple times in a workflow, duplicate methods are being generated instead of reusing the existing one. A code fix has been implemented to prevent the creation of duplicate methods.
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