Applies to algoQA V4.4.5, V4.4.6

• Code fix has been implemented to resolve the following bugs: 
  • Custom Tag Issue
    Previously, when custom tags with underscore values were provided while recording or editing a scenario, they were incorrectly displayed as hyphens in the Feature File. The backend code fix ensures that custom tags now display correctly with underscores in the Feature File.
    
    
  • Sorting Actions
    In the Java Appium framework, there was an issue with the default sorting actions (high to low and low to high) on mobile pages. The issue has been resolved for default sorting actions to function correctly according to the specified criteria.
    
    
  • Test Data.YML issue
    Despite enabling the data decoupling option in the Project Settings page, there was a problem where TestData was not generating in the TestData.yml file as expected. This issue has been resolved, ensuring that test data is now correctly generated and stored in a separate YAML file.
    
    
  • Prefix issue
    When a prefix with a number was provided in the Control Value textbox while configuring Nodes in Python Selenium (non web-enabled version), there was an issue where the prefixed alphabets were not generating correctly in the Feature File. This issue has been resolved, ensuring that prefixed alphabets now display accurately in the Feature File.
    
    

  • Duplicate Keys in Test Data.YML file
    During API test automation for negative test cases, duplicate keys were being generated in the TestData.yml file. This issue has been resolved to prevent the duplication of keys.
    
    

  • Data Set Generation Issue

    In web test automation using the Java Selenium framework, there was an issue where data sets uploaded in the Edit Scenario were incorrectly generating in both the Feature File and TestData.yml file. This issue has been resolved, ensuring that data sets are now generated in both files.
    
    

  • Report Generation Issue

    Reports were not being generated for large test cases in the web automation using the Python Selenium framework (non-web enabled version). This issue has been resolved to generate reports for large test cases.
    
    

  • Tool Tip Verification Error
    In the Java Selenium workflow, there was an error caused by extra spaces when using the verify tool tip action, leading to inaccuracies in tooltip verification. The backend code fix addressed this issue by eliminating unnecessary spaces, ensuring accurate verification of tooltips and improving the reliability of UI testing processes.
    
    

  • Scroll Vertically Default Action Issue
    In the Java Appium framework, there was an issue with the scroll vertically default action on mobile pages. The issue has been resolved to ensure that vertical scrolling functions correctly as per the specified criteria.
    
    

  • View logs Issue
    Previously, in the View Logs capability, search functionality was not functioning as intended. This issue has been resolved now, the search functionality works as intended.
    
    

  • Object Repository Issue
    Previously, there was an issue in TestComplete where UI element names fetched using the Object Spy tool were not reflecting in the Object Repository file. This issue has been resolved. When you use the Object Spy tool to fetch UI elements, their names will display in the Object Repository file.

    
    

  • Report Generation Issue
    In the iOS app using the Python Appium framework, HTML reports were failing to generate during batch execution of ten or more test cases. Reports were generated successfully only for batches of five or fewer test cases. This issue has been resolved, ensuring that HTML reports are now successfully generated during batch execution for ten or more test cases.
    
    

  • Storing multiple response value in store variable Issue
    In the API Test Automation, earlier user was not able to store multiple response value in store variable when they provide key and values in the 'Params' tab. For more information, refer to Adding Request Parameters to the specific Request Name This issue has been fixed so that user can store multiple response values.
    
    

  • Object Repository Improvement Issue

    In the Node Configuration, earlier when you specify different UI element names reflecting in two different pages with same XPaths, these XPaths were not reflecting in the Object Repository File. 

    This issue has been resolved, you can view same XPaths for different UI element names in two different pages in the Object Repository file.
    
    

  • Enhanced Response Output Display in Generated Reports
    In the API Automation, some of the test cases response outputs were not displaying in the generated Report.
    This issue has been resolved; you can see multiple output responses displaying in the generated report.
    
    

  • Report Generation Issue
    In the API automation, Extent reports were not generating Request Parameters and Actual values. This issue has been resolved, ensuring that extent reports are generated with Request Parameters and Actual Values.
    
    

  • Log Message Error in TestComplete workflow
    In the TestComplete Project Suite workflow, an indentation error is displaying for a particular workflow when using the checkbox as the Control Type. This issue specifically affects the "If" condition, causing indention errors in the log messages and disrupting the execution of the workflow.
    The indentation errors have been resolved. The If condition code blocks are aligned appropriately to ensure that log messages are formatted and the workflow executes as intended.
    
    

  • Object Repository Control Issue

    When a user tries to add a new control/UI element in the Object Repository, the error message 'duplicate control ID' is displayed, even if the control is not present. Additionally, even if values are already entered, the system prompts the user to enter the control/UI element name.

    A code fix has been implemented to prevent these error messages from being displayed. Users are able to add controls without any errors.

    To access Object Repository > navigate to the Main Canvas > More Menu > Edit Object Repository.

    
    

  • Auto Generate Test Cases Feature Issue
    When using the Auto Generate TestCases feature to generate test cases, UI elements/Controls were not reflecting in certain test scenarios.
    This issue has been resolved, and a code fix has been implemented at the backend to ensure that UI elements appears in the relevant test scenarios.
    To access Auto Generate Test Cases feature, navigate to the Main Canvas > More Menu >Auto Generate TestCases.
    
    

  • Incorrect Username Display Issue
    As a user, when you login to the algoQA platform, logged in user name is not displaying in the User Profile. 

    This issue has been resolved and code fix has been implemented so that logged in username is displayed. 

    To access user profile details> Login to algoQA > you can see your name displayed on top-right corner.
    
    

  • Incorrect Name Display in the Utility file
    In the centralized project, when accessing Utility files and when you hover on the utility lock icon, incorrect name is displaying.
    A code fix has been implemented to ensure the correct name is displayed when hovering over the utility lock icon.

    
    

  • API Automation Issues

    • Store variable issue 
      When storing values from the response of one API and passing the same variable name as a query parameter in another API, the values are not reflecting as intended.
      Code fix has been implemented to ensure that the stored values from the first API response are correctly referenced and passed as query parameters in subsequent API calls and scripts are executed without any issues.
      
      

    • Base URL Issue 
      When configuring an API with query parameters and storing the base URL in an environment variable file, copying the API to other collections or modules resulted in the URL being replaced by the base URL variable. Users were unable to change the URL. Base URL  serves as a starting point for API calls.
      Code fix has been implemented to ensure that when APIs are copied, the base URL variable is preserved as intended. It allows the users to modify the Base URL after copying.