Release notes V5.0.2

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

Enhancements

• Duplicate Step Definition Improvements
  A warning is now displayed when a single alias step is mapped to multiple actions (custom or default), helping prevent conflicts where only the most recent action was previously applied. Conflict detection works across setup files, with options to either apply the new action or reuse the existing one. 
  
  
• Test Cases Improvements
  Each test case now has a unique, auto-generated ID that is created once and remains unchanged, ensuring consistent identification.
  
  
• TestStep Settings Improvements
  A new test step setting, inlineWithoutTestData, has been introduced to support scenarios where custom or control values need to be embedded directly within the feature file. When this setting is enabled, the test data is treated as inline and is not included in the Examples table or external test data YAML file even when Data Decoupling is enabled. This enhancement allows greater flexibility by enabling direct inclusion of specific values within test steps.
  
  
• GWT Steps Improvements
  In the Web Automation and Python Selenium framework, users can now select multiple steps within a scenario and merge them into a single Given-When-Then (GWT) step. This merged step is automatically replaced with a newly created custom method, simplifying test cases, enhancing maintainability, and improving overall readability.
  
  
• Step Definition File Improvements
  Newly added steps are now appended to the bottom of the step definition file and sorted by "Step Create Date & Time" (earliest first). If timestamps are identical to the second, a secondary alphabetical sort is applied using the control name. Invalid or missing dates default to the earliest possible value, ensuring consistent and predictable ordering using standard Unicode rules.
  
  
• Feature File Improvements
  When using the same control (e.g., 'CN') multiple times with different custom values across scenarios, the generated YAML file now includes indexed naming for duplicate controls to ensure uniqueness. Indexing begins from the second occurrence, e.g., CN, CN_1, CN_2, CN_3. The first instance retains the original control name without indexing. 
  
   Bug Fixes
• Html Element json file issue
  

  In web automation, uploading multiple scraped files previously caused the HtmlElement.json data to be overwritten instead of appended. This issue has been resolved, and the data is now correctly appended as expected.
  
  

• Test Steps Settings Issue
  

  In the Scenario Steps List > Edit Step view, users were previously unable to select multiple test steps from TestStep Settings. This issue has been resolved, and multiple test steps can now be selected as intended.
  
  

• Scripts Generation Issue
  

  In algoQA, script generation was failing for copied projects due to the TestCaseGen folder not being cleared. A code fix has been implemented to ensure the folder is properly cleaned, allowing scripts to generate as expected with no workflow errors.
  
  

• Dashboard Report Issue
  

  In the Web Automation and JavaScript WebdriverIO framework, reports were not uploading to the dashboard unless the HTML file was manually replaced in the script. This issue has been resolved with a code fix, and reports now get uploaded to the dashboard without workflow errors.
  
  

• Create Project Page Issue
  

  On the algoQA Create Project page, when the page is opened using an algoScraper-scraped data , it loads for a few seconds. However, the page was also loading unnecessarily when a  scraped data  was not used. A code fix has been implemented to ensure that the Create Project page only loads when they have scrapped data from algoScraper.

   

• Action Name Issue
  

  The action "copied text not present" has been renamed to "verify copied text not present by index" for clarity. Additionally, the action now correctly performs a verification/assertion, instead of just returning a boolean, ensuring expected behavior during test execution.
  
  

• Dashboard Issue
  

  In the Web Automation and Python Selenium framework, an issue was identified where the dashboard became inaccessible after uploading reports, and the Timings section appeared as null. This has been resolved with a code fix. Reports can now be uploaded successfully, and the Batch Execution Result Table, including Tags, Status, and Comments, is displayed correctly as expected.
  
  

• Drag and Drop Issue
  

  In Test Design, the drag and drop, Move up and down features were inconsistent. A code fix has been implemented so that these features work as expected.