Versions Compared

Old Version 8

changes.mady.by.user Dhiraj Chandanshive (Unlicensed)

Saved on

compared with

New Version 9

changes.mady.by.user Dhiraj Chandanshive (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Qualitia Automation Studio 8.5.0 Release Notes

What’s New?

...

Publish Execution Results to ALM

Introduced a feature to publish the suite execution status to ALM test sets for the test cases that are executed in Qualitia suite.

Enhancements

...

  • Changes in Qualitia system properties will not prompt for restarting client

...

  • .

...

  • Updated the webdrivermanager version from 4.4.3 to 5.1.0.

Bug Fixes

...

  • Auto Heal (Smart Locator) support is added for web objects in SFDC Projects.

  • Fixed the AcceptDialogue action issue .

...

  • in SalesForce Automation.

  • The test data consistency issue related to loading the test case where step sequence in the included task is changed has been fixed.

  • Few bug fixes and enhancements are done to improve the user experience and product stability.

Engine

  • Fixed the opening of child window issue by loading the relevant polyfillsEnhanced multi-locator implementation for IE browser-specific polyfills. Multi-locator is now stabilized in the Chrome and Firefox browsers.

  • Updated the Wait action behavior as per the Qualitia Automation Studio 7.x series.

  • Fixed the Improved execution stability by fixing the use case which led to browser crash issue in the Qualitia v8.4.0 Offline packages.

  • Removed the unused dependency Perfecto-reportium-allure-integration library from the engine, which causes the following compilation error: Execution failed for task ':Reporter:compileJava'.

  • Qualitia Engine now applies the system properties that are

  • Fixed the issue where system properties entered by user in the Qualitia settings , and the were not utilized during execution.

  • The verbose logs for execution engine are now generated in the location specified by the user.

  • Bug fixes and enhancements are done to improve the user experience and product stability.

Known Issues

  • Execution of suites having test cases with large test data iterations, such as 5000 iteration rows and 500 parameter columns, fails to start.

  • While purging the old Qualitia Reports in large volumes, such as 16 GB reports with 44 GB data, you may see the "Error occurred while fetching purge listing" error.
    As a workaround, purge the old Qualitia Reports in chunks instead of purging large volumes at the same time.

  • Recording or executing test cases using Internet Explorer browser fails with a timeout error message in the QualitiaEngine.log file. This issue occurs as the WebDriverManager does not identify the IE browser version and hence it fails to download the appropriate driver.

    As a workaround, download and add a driver that is compatible with IE browser version manually and provide the path in Qualitia Settings by navigating to Browser>IE.

  • In the Dashboard Heatmap, if the date range spans across two calendar years, the heatmap shows the data only for the latest year.

  • In the Dashboard, for the date filters, the following behavior is observed:

    • If you select the current date, which is today’s date, the selection is applied.

    • If you select a date range, the starting date is applied but not the end date. Details up to the current date are displayed, irrespective of what end date is selected.

    • If you select a date from previous years, then the selection is ignored. Data for only the current year is displayed.

  • When you purge more than 2 GB of data, the purge status of the batch is not marked as completed as expected.

  • In the Dashboard – Test Trend, the unexecuted test cases from a suite are not included in the calculations.

  • Overriding an environment variable that is used in multiple QAS projects from the Azure DevOps pipeline overrides the environment variable across all QAS projects.
    You can use any of the following workarounds:

    • Do not use the same environment variable name across multiple Qualitia projects that are linked with an AzureDevOps project.

    • If you already have an environment variable that is used across multiple Qualitia projects with AzureDevOps pipeline, do not override the environment variable from AzureDevOps pipeline.

    • Ensure that the tests from different Qualitia projects are not linked to the AzureDevOps tests in the same test suite.

    • Ensure that environment variables names in multiple Qualitia projects do not match. You may prefix them with the project name.

...