Applies to algoQA V4.4.6

• Code fix has been implemented to resolve the following bugs: 
  • algoscraper Issues 
    • A few XPath expressions for a given web application were not functioning as intended.
      The issue has been resolved by implementing the code fix.
    • Previously, when using the Scrape UI button, as a user, you could download the scraped file even if you don't select a Control Type or include multiple spaces in the Control Name. A bug fix has now been implemented to display an error message if the Control Type is not selected or if additional spaces are entered in the Control Name.
      
      
  • Hybrid Test Automation Issue 
    In the Hybrid Test Automation, when you update the App Activity, App Package, and Bundle ID in the Project Settings page, the updated values were not reflecting in the Application Settings file. This issue has been resolved with a code fix, and you will see all the updated values reflecting in the Application Settings file.
    
    To access After generating the script, download it to your local folder. This folder must contain the script file that you have generated. Open the folder where you downloaded the script. For example, if your script is located at AlgoAFScript_202402121131\src\test\java, navigate to this folder. Applications.xml file will be available in the Java folder.
    To access Project Setting Page: Navigate to the Main Canvas and select Project Settings icon ().
    
    
  • Report Generation Issue

    Reports were not being generated for test cases in the mobile app automation using the Python Appium framework, and Report.exe command was not working as intended. This issue has been resolved, and code fix has been implemented to generate reports using algoReport.exe command.
    
    

  • Traditional API workflow- Parameters Tab Changes Reflect in API URL
    In the Generate Script screen of the traditional API workflow, when you update the key and value in the Parameters tab, they did not reflect in the URL while editing an API.
    A code fix has been implemented, and parameter values are reflecting in the URL.
    
    

  • Output Folder remains empty after sending reports via email

    When algoQA generated reports are attached to the recipient's email, no reports are found in the designated Output folder. The generated reports are created in a zipped format, but they are stored outside of the output folder.

    A code fix has been implemented to ensure that the reports remain in the Output folder after being sent via email.

• Utility File lock functionality Issue

  In the Code Editor screen, the lock functionality for the Utility file was not working as intended.

  The code has been updated to ensure that the active user's name is displayed when you hover over the lock icon.

  
  

• Custom Action Deletion Functionality Issue 
  After deleting a custom action, users can still call the deleted action method, indicating a functionality issue. The code fix has been implemented to prevent execution of deleted actions and ensure all references are removed upon deletion.

  
  

• Copied Default Action Issue 
  The Copied Text action, when used multiple times, is not functioning as intended.
  The action copies the copy text from the element and store it globally, but it fails to perform this function after multiple uses.
  A fix has been added to make sure the "Copied Text" action works properly, even when used multiple times.