Applies to algoQA V4.4.9

• The algoReport.exe file Issue
  The algoReport.exe file is not generating ALM files as intended, so reports couldn’t be attached to recipient email using the algoReport.exe command. A code fix has been implemented to ensure ALM files are generated and attached to recipient emails when sending reports.
  
  
• Script Generation Issue
  In the Desktop automation using C# Winappdriver framework, Script is not getting generated without locator information for any UI Elements (controls) when there is missing control ID information in .XLSX file in the Test Cases Folder. A code fix has been implemented to ensure scripts are generated without Locator.
  You can access Test Cases Folder in the appropriate project folder.
  
  
• ApplicationSettings.xml file Issue  
  In the ApplicationSettings.xml File tags, earlier  it was reflecting as LamdaTestAppKey Tags even for Browserstack integration tags. A code fix has been implemented to reflect as BrowserStackAppKey Tags. You can access ApplicationSettings.xml file in the algoQA script generated folder.
  
  

• API Automation Issue
  In API automation, the browser is incorrectly launched during the execution of the API. A bug fix has been implemented to prevent the browser from launching while executing the API.
  
  

• Restore Functionality Issue

  The Restore functionality, API is not responding as expected in the Production environment. Instead of returning an appropriate response, the API request goes into a pending state, causing delays and preventing the restore operation from completing.

  A code fix has been implemented to address the bug. The Restore functionality API now responds with the appropriate success or failure status and no longer stays in a pending state.

• Mobile Automation Issues 
  In Mobile Automation using Python Appium, where the verify duplicate records action (checking for duplicate XPath elements) and the compare and verify images action (it takes the image of a particular screen when EnableCompareImage is false in ApplicationSettings.xml, and if EnableCompareImage is set to true, it compares the newly taken screenshot with the previously captured image; if they don't match, the test fails) are not working as intended. You can access ApplicationSettings.xml file in your algoQA script generated folder. A code fix has been implemented to address the issues.
  Earlier reports were generating only for passed scenario. The issue has been resolved and reports are generating for both passed and failed scenarios.