Versions Compared

Key

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

...

  • 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 /wiki/spaces/T2/pages/2681539904 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 messages in custom actions.
    Failure classification gives more actionable insights to users to work on.

...

Real Time Reporting

Now get suite execution results at in 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

...

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

  • Support for empty objects in the desktop type of projects

  • Debugger support for desktop projects

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

...

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

...

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

...