Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 84 Next »

What’s New in this release?

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.

New Features

Introduced the Keep Dry Run Reports option, which does not overwrites the reports of the previous dry runs. For more details, refer to Dry Run a Test Case.

Bug Fixes and Enhancements

Enhancements

  • The QAS server upgrade process now handles the Unit Test stubs for the projects integrated with TFS/Azure DevOps. You are no longer required to re-publish the test cases after upgrading the TFS/Azure DevOps integrated projects.

  • Significant performance improvements have been made in the following areas:

    • Test case management

    • Object management

    • Project management

    • Local data cache management

    • SaveAs Project feature

  • The location of TFS/Azure DevOps Remote Agent working folder has been moved to the localappdata folder to avoid conflicts.

  • Cosmetic user interface changes done to improve the user experience.

  • Enhancements in the object identification for web element with text in IE object spy.

  • Enhancements in the SmartLocator algorithm.

Bug Fixes

  • Qualitia Automation Studio now allows you to save test cases with empty test data (cells containing only spaces).

  • Fixed the issue related to the data type while passing variables to the Vbscript engine for the test case executions on the Desktop applications.

  • Fixed the issue with test case exit flags in a test suite. When you save a test suite, the existing test case exit flags do not reset to Continue (Green flag) anymore.

  • Fixed the issues related to the test data of the projects that are migrated from QFD. Now the correct test data is shown for those actions whose parameter sequence has changed.

  • Minor fixes related to object identification are done.

Known Issues

  • The following error message appears when you open a test case of a project that is migrated from QAS v7.x:
    Object Reference not set to the instance of the Object.
    To work around this issue, after you complete the project migration, delete the DBCache folder, which is located at the following location:
    %localappdata%\Qualitia\WD\Client\Settings\<Project Folder>\DBcache

  • The QAS client crashes if it remains idle for more than 12 hours on a virtual machine.

Qualitia Automation Studio 8.0.2 Release Notes

Dropped Feature

Qualitia has dropped MOS and Qualitia Automation Mobile Recorder support for iOS version 10.4 and earlier.

Bug Fixes and Enhancements

  • Removed check-in of DBCache and environment variables in Git to avoid conflicts when using Git as the version control system.

  • Improved the Object Selection performance in the Test Case Editor screen.

  • Fixed the synchronization issues between Qualitia Design Studio and Qualitia Automation Studio.

  • Fixed the issue related to publishing custom actions during Azure DevOps integration.

  • Fixed the issue where custom action execution in Azure DevOps integration was skipped intermittently.

Known Issues

Known Issues in Settings

  • QAS client does not prompt any error message if the Java path is blank in the General Settings screen.

Known Issues in MOS and Qualitia Automation Mobile Recorder

  • MOS and Qualitia Automation Mobile Recorder do not support iOS versions 14.x and later.

  • Hovering over a web element may fail to highlight the web element if the page contains multiple iframes. In this case, MOS/MR displays the "Failed to execute method" error message.
    To work around this issue, Qualitia recommends to record the web element using the Qualitia Automation Web Recorder for the specific step.

Known Issues in QDS Integrated Project

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

  • QDS does not display the mobile objects having UIAutomator locator type. Hence, while using MOS or Qualitia Automation Mobile Recorder, in the locator type precedence settings, set UIAutomator to lowest. Also, replace the locator types for the objects having the UIAutomator locator type with another locator type. 

Qualitia Automation Studio 8.0.2 Release Notes

New Feature

Introduction of Rest.Patch.Execute.API action.

This PATCH API action updates the partial resources, which can be used as an alternative to the PUT API action. Typically, PATCH API actions are light-weight and consume less bandwidth when compared to the PUT API actions. For more information, refer to Rest.Patch.ExecuteAPI.

Dropped Feature

Mobile Object Spy and Qualitia Automation Mobile Recorder has dropped supporting iOS versions 10.4 and earlier.

Enhancements

  • Multiple enhancements are done to the user interface to improve usability.

  • Improved the error message that is displayed when you create a project that already exists in the target database server.

  • Improved the error message to highlight the set of characters allowed in a project name while creating a project.   

  • Enhanced the info logs for wait actions. Info logs now display the actual values used in wait action executions.

  • Added support to integrate Azure DevOps Git repository as a version control tool in addition to Bitbucket and GitHub.

  • When a user edits a task, other users can now view the following information:

    • The user who edited the task

    • The date and time when the task was edited

    Earlier, only the following message was displayed:

    "Some tasks in the test case have been modified".

  • Added support for specifying a relative path to the AttachFile action.

  • Added support to update the expired password in the ALM integration settings.

  • Added support to update the expired password in the Azure DevOps integration settings.

  • Added support to install Qualitia Automation Studio for multiple user profiles on a Virtual Machine even when other users are actively using Qualitia Automation Studio.

Fixed Issues

  • Fixed an issue related to the latest setup files for Qualitia Web server setup not getting updated to the latest version during the Server upgrade process.

  • Fixed the issue where the IF conditional statements that were migrated from QFD did not work.

Known Issues

Actions

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

Mobile Object Spy and Qualitia Mobile Recorder

  • When capturing an object on an SMS application, the object name is appended with null.

  • Unable to start a session after selecting an application in MOS or Mobile recorder on Xcode version 11.6 or higher. To work around this issue, refer to Unable to Start a Session on Xcode.

  • MOS and Qualitia Automation Mobile Recorder do not support iOS versions 14.x and later.

Mobile Object Spy

  • Clicking any object field displays the following message unnecessarily:
    ”Object updated successfully”

  • For an empty object, if you click its object class, the locator type is automatically selected as ID.
    To work around this issue, from the Locator Type drop-down list, select the desired locator type you want.

  • The empty object scenario does not work correctly on iOS.

  • No error message is displayed when you click the locator field values for an empty object. However, you can edit the empty object normally by selecting the class, type, and value.

Qualitia Automation Studio 8.0.1 Release Notes

Enhancements

Bug Fixes

  • Fixed the minor issues in UI, suite executions, and configuration settings.

  • Fixed an issue related to Offline Suite executions.
    An offline suite execution fails if it contained an encrypted password that is defined in the associated Environment Variables.

Known Issues

  • The Web Dashboards display the execution results as per the time zone of the QAS server. However, the Realtime Reporting portal displays the execution results as per the local time zone of your computer.

    Hence, for the suite executions that occur in a time zone different than QAS server’s time zone, the date and time for the execution results displayed on Real Time Reporting Portal and Web Dashboard might be different.

Qualitia Automation Studio 8.0.0 Release Notes

In this release, we have gone the extra mile to enhance your test automation experience. This new and improved version will help you to build robust tests like never before.

New Execution Engine

  • UI for Offline Package: Update Qualitia settings and capabilities which are needed for offline executions. There is no need for a manual update of properties or JSON files.

  • Execution Profiles: Create different profiles for a suite that you can execute against them. For example, profiles for cloud execution, local execution, and remote execution.
    For more information, refer to Working with Execution Profiles.

  • Stop Execution: Stop execution in between a Dry run or Suite run from QAS itself.

  • Support of object data type in StoreHashMap: Store and read any Java object in StoreHashMap in custom actions.

  • Failure Classifications: Now provide failure reasoning along with step message in custom actions.
    Failure classification gives more actionable insights to users to work on.

Qualitia Automation Studio Recorder

Now record operations performed on the application under test and convert them into ready-to-execute automation test cases. Qualitia recorder automates and simplifies the process of creating test cases. This feature allows you to

  • 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 Recording a Test Case using Qualitia Automation Studio Recorder .

Real Time Reporting

Now get suite execution results at real time.  The Real Time Reporting Tool allows you to monitor the test suite executions that are in progress. It updates the results of a test suite execution in real-time as each test case iteration is executed. Using this feature, you can:

  • Access logs & screenshots for test case executions

  • Monitor all Suite executions in real time, including offline executions

  • Access execution reports of all the suite executions run by all users in a project

  • View offline reports at the end of each test case iteration

  • Access reports for even aborted executions up to the point of failure

  • Improved compatibility to view results with popular browsers

For more information, refer to Real Time Reporting Portal .

Single Offering for Desktop, Web and Mobile

Now use the same Qualitia version for testing Desktop and Web/Mobile applications.

  • Additional features of Web projects will now be available for desktop projects as well·        

  • Support for empty objects in desktop type of projects

  • Debugger support for desktop projects

  • Error navigation in test case and tasks for empty/deleted objects

Additional Features

  • Apply settings for custom actions and version control at a project level. This means that you can create different settings for different projects.

  • Create multiple execution profiles and select a particular execution profile during suite execution. An execution profile is a pre-defined set of configuration settings, which can be used to execute test suites. You can add multiple execution profiles with the different combinations of configuration settings. Use the new user interface for editing profile settings and desired capabilities.

  • Maintain multiple execution profiles for an offline package and edit the profiles using a simple user interface.

  • Developing Custom Actions has become more object-oriented as you can access Qualitia Public APIs.

Known Issues

The following are the known issues in Qualitia Automation Studio 8.0.0.

Qualitia Automation Studio

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

TFS/Azure DevOps Integration

  • The Qualitia Remote Agent resets the execution settings when you upgrade to Qualitia 8.0. In this situation, you must configure the execution settings again.

Qualitia Automation Recorder

Common Issues

  • If the XPath locator value for an object contains a Unicode value, it is taken as a blank space while dry run and suite execution. As a result, the execution fails as Qualitia does not identify the object.

    To work around this issue, edit the object using a locator type other than XPath.

  • While a recording session is active, if you dry run the test case and then stop it manually, the recording session also stops.

Qualitia Web Recorder

  • If you start a recording session and close the browser immediately, the recording session does not stop automatically. Also, you need to close the recorder launching progress bar using Windows Task Manager.

  • Before recording the verify and wait actions for a table, you must select the table.

  • Qualitia Web Recorder does not support Shadow DOM.

  • If you use Internet Explorer for recording, you can record the objects of the Security Certificate dialog box. However, when you dry run the test case, the recorded steps associated with the Security Certificate dialog box fail.

Specific to SFDC Application

  • You cannot record the actions on the objects of permission request popups. To work around this issue, you need to manually add the steps with actions such as AcceptDialog and DismissDialog.

  • If you select an item from a list, the recorder does not record the SelectItemByText action, but it records a step with the Click action and the selected list item as the object.

Qualitia Mobile Recorder

  • You cannot record the objects when launching the application in the Android device, the auto-fill popup appears. The workaround is to disable the auto-fill popup.
    You can disable the appearance of auto-fill popup in the Android 10 device as follows:

    Settings >> Language and Input >> Autofill service >> Click and select option as None     

    For other Android versions, you need to check with the relevant Android Version documentation.

     

  • Qualitia Mobile Recorder does not support recording web and hybrid applications on an Android emulator that is connected to a Macintosh agent.

  • Simulators and real devices having iOS version 13.3 do not support native applications.

  • The following iOS platforms do not support recording and Mobile Object Spy for the web applications and web-view context of hybrid applications:

    • All the iOS simulators versions

    • Real devices having iOS version 12.2 or above

  • For the projects upgraded from the previous Qualitia versions, if you record a test case, then for every object, multiple pages and objects are created in the object repository.

    To work around this issue, after upgrading the project, change the locator type and value of the Page object to XPath and “//app”.

  • Unable to connect to a device intermittently. To work around this issue, restart the recording session.

  • While recording a web application, if you update the URL in the address bar, it is not recorded as a step. You need to enter a step manually with action as OpenURL and add the new URL in the parameter.

Reports and Dashboard Portal

  • If you have not specified an operating system version in the associated execution profile for suite executions on SauceLabs and BrowserStack, the Real Time Reporting Portal does not display the operating system version for these suite executions.

  • If you change the defect management system for a Qualitia project, then the suite execution summary reports that are already open in the browsers show the old defect management system details to log a defect manually.
    In such situations, you can log in to the Real Time Portal or access the Test Suite Execution Summary report from the Suite of Suites screen to log a defect manually using the new Defect Management System.

  • For the desktop applications suite executions, the execution time for the first test case iteration does not include the UFT launch time. Hence, for these suite executions, the execution start time shown in the Real Time Reporting Portal and Web Dashboard differ.

  • If you are using Firefox to access the Real Time Reporting portal, the white borders in the table grids for the reports are not displayed. This is caused due to a known issue in Firefox.

  • For a test case step, you can edit the text under Name/Condition column in the test case editor screen and save the test case. However, after executing the associated test suite, the Suite Execution report screen displays the original test under the Hierarchy column

  • The design of Real time Reporting Portal is not mobile responsive. Therefore, you can expect some UI distortions when viewing the portal through the mobile device having a resolution lower than 1100px.

Custom Actions for Desktop Projects

  • You cannot add or remove parameters from a custom action for a mapped function on Custom Action window. To work around this issue, launch the associated VBS file from Qualitia client, add or remove parameters for the mapped function, and remap the function to the custom action from Custom Action window.

  • No labels