...

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 are happy to announce the release of Qualitia Automation Studio 8.3.4.

...

• 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

...

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

...

• Create test cases for Web/Mobile applications, or a combination of both.

• Capture the actions performed on the application as steps and store them as objects, along with the associated actions and parameters.

• Pause recording whenever needed. Start/Resume recording from any step in the test case editor. Use the Test Case Editor to group the steps under separate tasks
  For more information, refer to (8.3.X) Work with Test Cases https://qualitia.atlassian.net/wiki/spaces/QASNew/pages/34343125975 https://qualitia.atlassian.net/wiki/spaces/QAS83X/pages/3367210334/Recording+a+Test+Case+using+Qualitia+Automation+Studio+Recorder?src=search.

...