Versions Compared

Key

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

...

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

  • 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

...

  • 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

...

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

...

  • In Project Save As Feature, the custom action files from the source project are not moved automatically to the target project. After the project is saved, you need to manually move the dependent jars and Custom Action Function codes associated with the custom actions (keywords) that were selected during Save As process.

  • When editing a test case, if you make any changes and go to the search box to search a test case without saving the changes, you are prompted to save the changes. If you click Yes, the Scenario tree shows the test case with matching criteria, but the changes are not saved. You must save the changes that you made to a test case before you perform a search on the Scenario tree.

  • In a desktop project, if you search for an object that is a part of a long hierarchy in the Objects tree, clicking Next does not scroll up to the highlighted object.

  • The Desktop web executions are not tested on Macintosh computers.

  • Execution of test case steps on Web and Hybrid Apps using Android emulator takes a longer time.

    To work around this issue, do one of the following:

    • Open the mapped execution profile and disable all the options of Screen Capture On .

    • Open the mapped execution profile, click Mobile > Edit Desired Capabilities, and set nativeWebScreenshot to true.

  • The Click action may fail to execute if the Mobile checkbox object is added using the ID locator type. To work around this issue, use XPath locator type for adding the Mobile checkbox objects.

  • The Mobile.SelectWebViewUsingURL action may fail on some versions of iOS. During testing, the action failed on Simulator iPhone 8 with PlatformVersion 13.3.

  • Qualitia does not support nested environment variables. The test cases that were created using previous QFD versions, having nested environment variables will fail upon execution.

  • Qualitia supports only basic data types such as Number and List/Option, for integration with Defect Management Systems (Jira and TFS). Qualitia does not support complex data types such as custom user-defined data types, nested objects, and dates.

  • If you switch to another project from the Qualitia client, the current MOS session does not change. To work around this issue, log out from MOS, log in again, and select the correct project.

...