Introduction

These release notes provide information about the new features added to Qualitia Automation Studio. They also provide details about the enhancements done, bugs fixed, and known issues in this release.

We’re excited to announce Qualitia 8.5.0. In this new version, we have fired up Qualitia with exciting new features and capabilities to improve the overall user experience.

We have also resolved some long-standing inefficiencies that will go a long way in providing the required stability to your automation. And we have enriched Qualitia with functionalities to ensure successful test automation at enhanced performance levels.

...

Export real-time reports to ALM and share across teams 
We have spruced things up and made it possible for you to export real-time reports to ALM with the same folder hierarchy structure as in ALM and using the same search test case functionality. The best part is that you can now share reports across teams and stakeholders for a better understanding of execution and test coverage and gain better insights into defects/failures in the application under test. 

Incorrect mandatory failure of action is mandatory no more! 
In this new version, we’ve tinkered with the internal working of Mobile.CloseApp to avoid mandatory failure of action when the mobile app is not launched before using the CloseApp action. 

Easy to understand error messages  
When a step fails after using an incorrect environment variable to get the locator value, we have made the error message clearer to help you understand the exact cause of failure and make relevant corrections. 

Silent update and restart  
Now, you don’t need to manually restart Qualitia to update any configuration change. We have made changes in Qualitia system properties, enabling the engine to update the changes and silently restart on its own.  

Added Auto Grant Permission capability  
If you were not able to see the AutoGrantPermissions property in Qualitia version 8, we have added the capability for Android mobile platform now. After defining the execution behavior, the user can auto grant permissions for the application under test.  

...

Better execution stability   
With Qualitia 8.4.0 offline packages, the browser was crashing and that resulted in showing incorrect execution status, leading to false reporting. In the new version, we have fixed the browser crash issue for better execution stability. 

Improved test data management  
The test data mismatch error encountered when saving test cases where the task was modified from the task tab by another user is now fixed. The new release has made it easier to make changes to the task from the task tab as well. 

Enhanced execution profile functionality 
Previously, when changes were made to the execution profile, they were not getting saved. We have made a few modifications in the saving execution profile data to make the execution profile functionality stable.  

Improved dashboard usability  
There were issues with the dashboard, including duplicate key entries, blank dashboards while switching projects, sort order functionality not working properly, and heatmap showing the wrong data range. The new version has proactively resolved these issues to provide a seamless experience.   

Resolved memory leak for smooth navigation to test cases  
The intermittent crashes of Qualitia while navigating to different test cases, which were traced to store history data in the memory now stand resolved. In this new version, the memory leak is fixed by clearing the last visited page/frame from history to reduce memory consumption. 

Enhanced multi-locator implementation for web applications 
If in the older version, web application child window was not opening when clicked, we have now enhanced the multi-locator implementation by loading the relevant polyfills. The multi-locator is now stabilized for Chrome and Firefox browsers. 

Handled TimeoutException for uninterrupted execution 
We have made changes to the TimeoutException in action to stabilize the AcceptDialog action for robust execution.
 

Stabilized task step addition process  
Previously, whenever a new step was added to the test case task, multiple clones of the step were automatically updated. In this new release, we have improved the stability of task step addition by adding a task navigation handler in the constructor of the task that stops multiple cloning of steps.  

Enhanced the scope of Chrome Object Spy 
With a few changes in the identification algorithm, we have improved stability of object locator creation for Large Object Hierarchy in DOM structure for Chrome Object Spy. 

Fixed wrong error displayed during the upgrade 
During the upgrade, an incorrect error that the Qualitia server is in maintenance mode was displayed. We’ve now removed the code that was responsible for this invalid connection string.  

...

Faster fetching of records from the database   
During upgrading the Qualitia server from 8.4.0 to 8.5.0, the query execution was taking more time than configured to fetch the records from the database. We have fixed the upgrade issue related to databases with latency issues.  

Extended SmartLocator capability in SDFC projects 
Qualitia 8.5.0’s SmartLocator now supports web objects in SFDC project type. This corrects locator values for objects which usually fails during object identification. This means less maintenance overhead and more robust execution.  

Adding/updating task steps from the task page is now faster! 
The slowness while updating or adding task steps from the task page were addressed in this new version. Now, there is no unnecessary delay while task development. 

Quicker loading of test cases  
There was a performance issue while loading test cases, which was not seen in the installed production v8.3.1. In this new version, we have reverted the changes related to test case loading back to version 8.3.3. This has drastically improved the performance of the test cases screen for test cases loading.  

Enhanced UFT support 
This version supports UFT version 2021. This means Qualitia 8.5.0 has all the latest API access for desktop automation. 

...

• 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.

• For test cases aborted inside Suite of Suites, the execution time shows 0hr 00m 00sec. This is only for jobs which get aborted due to service restart.

• 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.

...

• You can now link multiple Qualitia projects to the same project in Azure DevOps. You can manage your testing efficiently by organizing all Qualitia projects separately under a single Azure DevOps project.

• You can now link multiple Qualitia test cases from different Qualitia projects to a single manual test case cases in a single Azure DevOps project.

• You can now see a consolidated report for multiple Qualitia projects.You can now quickly search the Azure DevOps Test Plan and Azure DevOps Test Suite while linking the Qualitia test case to Azure DevOps test case instead of scrolling from the drop-down list to save time.

...

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

• When a step inside a task that is being moved down crosses over another step being moved up, the test data of the test cases using the task being moved goes into inconsistent state. This issue is observed only when two test steps being moved in opposite direction cross other.

• 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.Overriding an environment variable that is used in

• For test cases aborted inside Suite of Suites, the execution time shows 0hr 00m 00sec. This is only for jobs which get aborted due to service restart.

• 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.

...

• The QAS Recorder and Object Spy now generate the same CSS locator value for Shadow DOM objects.

• The Smart Locator is now supported with SFDC objects now supports web objects in SFDC and normal objects.

Qualitia Automation Studio 8.3.4 Release Notes

...

• You may experience performance issues when editing a test case with large volume of test data associated with it.

• Execution fails to start for the suites having test cases with large test data iterations.

• Test data gets corrupt when the task steps are moved up or down.

• Mobile Object Spy, Mobile Recording, and Mobile execution do not support Android real devices and emulators with Android 11 operating system and above.

• Internet Explorer (IE) does not support Shadow DOM. Hence, IE Object Spy and IE Recorder do not support Shadow DOM Object Spying.

• For test cases aborted inside Suite of Suites, the execution time shows 0hr 00m 00sec. This is only for jobs which get aborted due to service restart.

• SFDC objects do not support the following features:

  • Polling Interval and Time Out on object level

  • Wait actions

...

• SFDC.SwitchUser: Qualitia Automation Studio now also record and execute Switch action. You can use this manually and execute.

• SFDC.GlobalSearchAndClickSearchAndClick: Qualitia Automation Studio now also lets you record and execute GlobalSearchAndSelect action. You can use this manually and executehas introduced a new SFDC class called SFDCGlobalSearch that lets you perform and record global search for a particular user. This class allows you to record the SearchAndClick action along with its parameters and associated objects.

Enhancements in SFDC Project

...

• FireFox Recorder uses the SetWindowSize action instead of MaximizeBrowser when the browser is maximized during recording.

• Currently, Mobile Object Spy and Mobile Recorder do not support the Shadow Dom feature.

• The "Highlighted object(s) does not exist on the current page" error message occurs for all objects even if the objects are highlighted. This is an intermittent issue for Object Spy.

• In Shadow DOM, Web ObjectSpy and Web Recorder do not support element with dynamic attributes which have non-null attribute value.

• Unknown error exception occurs while performing actions on the Shadow DOM object:
  For the Click and MouseOver actions, you can use the alternative actions ClickJS and MouseOverJS, respectively provided by Qualitia.
  For similar issues with other actions, contact Qualitia Customer Support.

• Test Case execution from ALM fails when the integrated Test Case is locked or out of sync, when the associated task is modified by some other Test Case or from the Task tab.
  To work around this issue, unlock the Test Case or open and save the impacted test case, and then execute the Test Case again from ALM.

• Commit from GIT fails for long file paths, though it works from GIT Bash. For example, C:\Users\localadmin\Documents\DND_QDS_Automation_Backup\DND_QDS_AutomationProject\Regression_Repo.
  To work around this issue, use short file path. For example, C:\.

• Mobile execution with the “_appiumOption” capability as “Automatic” does not work With ALM integration. ALM does not allow to connect to the appium server even when the server starts successfully at the localhost. Once ALM is disconnected, the appium server is connected successfully, and the TC executed as expected.
  To work around this issue, set the capability "_appiumOption" as "custom".

• For test cases aborted inside Suite of Suites, the execution time shows 0hr 00m 00sec. This is only for jobs which get aborted due to service restart.

Qualitia Automation Studio 8.3.2 Release Notes

...

• FireFox Recorder uses the SetWindowSize action instead of MaximizeBrowser when the browser is maximized during recording.

• Currently, Mobile Object Spy and Mobile Recorder do not support the Shadow Dom feature.

• The "Highlighted object(s) does not exist on the current page" error message occurs for all objects even if the objects are highlighted. This is an intermittent issue for Object Spy.

• In Shadow DOM, Web ObjectSpy and Web Recorder do not support element with dynamic attributes which have non-null attribute value.

• Unknown error exception occurs while performing actions on the Shadow DOM object:
  For the Click and MouseOver actions, you can use the alternative actions ClickJS and MouseOverJS, respectively provided by Qualitia.
  For similar issues with other actions, contact Qualitia Customer Support.

• Mobile execution with the “_appiumOption” capability as “Automatic” does not work With ALM integration. ALM does not allow to connect to the appium server even when the server starts successfully at the localhost. Once ALM is disconnected, the appium server is connected successfully, and the TC executed as expected.
  The workaround to this issue is to set the capability "_appiumOption" as "custom".

• For test cases aborted inside Suite of Suites, the execution time shows 0hr 00m 00sec. This is only for jobs which get aborted due to service restart.

Qualitia Automation Studio 8.3.1 Release Notes

...

• Fixed the issue where the SVN client version was getting reset in the Scheduler suite executions.

• Updated the custom action return status handling when the return status values are not as expected by Qualitia.

• Now, you cannot edit the test data if all the test case steps use static data.

• Fixed issues in action execution.

• Fixed the issues where the suite execution results displayed cropped screenshots in different screen resolutions.

• Improved the Excel.StoreCellData action to read different data types from an Microsoft Excel file.

• Improved the performance of the Suites and Custom Actions screens.

• Improved the Settings screen.

• Some cosmetic changes are done in the product to improve the user experience.

Known Issues

• Before executing a test case or a test suite on a custom browser profile, ensure that you close all the instances of the browser.

• For test cases aborted inside Suite of Suites, the execution time shows 0hr 00m 00sec. This is only for jobs which get aborted due to service restart.

Qualitia Automation Studio 8.3.0 Release Notes

...

• The mobile native and hybrid application file, that is the apk, ipa, and app file, is not uploaded on Perfecto automatically during the Qualitia Automation Studio executions.
  Qualitia recommends that you perform the following steps to upload the native and hybrid mobile application file:

  1. You must upload the mobile native or hybrid applications on Perfecto Cloud before executing test suites.
     To upload a mobile app, login to Perfecto website, click Assets and Setup>Upload.

  2. After uploading the mobile app, copy the Perfecto lab repository path for your mobile app.

  3. Enter the Perfecto lab repository path in the first parameter of the Mobile.OpenApp action.

Qualitia Automation Studio 8.1.0 Release Notes

...

• While upgrading from a previous QAS version, the saved browser binary does not work correctly. This causes the browser to close immediately when you are recording a session.
  To work around this issue, update the browser binary to replace the existing browser binary even if it is the same at the following location:
  %localappdata%QualitiaWDClient/Selenium

• The Excel.WritetoColumn and Excel.WritetoRow general actions are not working correctly.

• During a MOS or Mobile Recorder Session, if you switch from a native-context to the web-context view, the web-view may get distorted for an iOS hybrid application on a real device having iOS version 12.4.5.

• While recording a hybrid application, by default, the Page Refresh option is set to Auto mode by in the web view context.

• The SelectWindowUsingURL action may sometimes fail to execute on Internet Explorer.

• During execution, if you switch from the native-context to theweb-context of the hybrid application, the screenshots for the steps executed on the web-context are not displayedin the Execution Summary Report.
  To work around this issue:

  1. Open the associated execution profile.

  2. Click Edit Desired Capabilities > Android.

  3. Select the nativeWebScreenshot checkbox.

  4. Set nativeWebScreenshot to True.

  5. Click Update.

• In desktop projects, if you add a test data with a double quote, it is replaced with an empty data.

...

• If you create a task using steps of a test case in QAS, then QDS does not display the updated test case and the created task.

• Changing the order of tasks in QDS for the test case which has a Test Data in QAS corrupts the test data in QAS. Also, you cannot edit or save the test case in QDS.
  To work around the issue, perform the following steps:

  1. Export the test data of the affected test case. This allows you to use the test data partially again.

  2. Detach all the tasks and remove all the TC steps from the Test Case in QAS.

  3. Import the same tasks in the required order and add the TC steps again at the appropriate places. However, you need to add the test data again using the data from the exported excel sheet appropriately.

Qualitia Automation Studio 8.0.2 Release Notes

...

• The WindowsAuthenticationLogin action does not work on Safari.

• The PressKeys action does not execute on the inactive screen of the VM for the following keys and key combinations.

  1. NUMLOCK

  2. CAPSLOCK

  3. SCROLLLOCK

  4. PRTSC

  5. Ctrl+Shift+Tab

  6. Ctrl+N

  7. Alt+F4

  8. Ctrl+Shift+T

  9. Ctrl+W

  10. Ctrl+F4

  11. Ctrl+F5

  12. Alt+Home

  13. Ctrl+

  14. Ctrl-

  15. Ctrl+Shift+Del

  16. Ctrl+J

  17. Ctrl+P

  18. Ctrl+O

  19. Ctrl+U

Defect Management Systems

• The defect management system integration settings are not preserved during migration to 8.0.x. After completing the migration, you must manually re-configure the defect management system integration settings.

• You cannot directly change the settings in the Defect tab of Project Settings if you want to replace the mapping of a Qualitia Project to another Jira/TFS project.
  To replace the mapping for a Qualitia project with another Jira/TFS project, perform the following steps: 

  1. Do one of the following:

     • Go to Admin > Project, under the Configuration column, click Configure next to a project.

     • Go to Settings > Project Settings.

  2. Click the Defects tab.

  3. Select the Target Defect Management System to None.

  4. Click Ok.

You can now integrate the Qualitia project with another Jira/TFS project. For more information, refer to Defect Management Systems .

...