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.

This article includes the following topics:

What’s New in this release?

Taking another step towards our goal of making test automation faster, simpler and more reliable, we are proud to announce the release of Qualitia Automation Studio- 8.0.0 Beta.

Qualitia Automation Studio Recorder

Now record operations performed on the application under test and convert them into ready-to-execute automation test cases.

How Does It Help?

• Faster Automation: Users do not need to worry about writing test cases manually. The object identification also happens during the recording process itself. The whole process of automation becomes considerably faster, thereby significantly reducing time-to-market.

• Easy-to-use: The recording of a test case happens while the application under test is being used. Any user with less or no knowledge of automation can use this feature to record ready-to-execute automation test cases.

• Lesser Manual Error: By eliminating the need to write test cases manually, Qualitia ensures that the test cases are less prone to manual error.

• Validate the Test Cases: The user can validate the automation test cases by replaying the recording.

For more information, refer to Recording a Test Case using Qualitia Automation Studio Recorder .

Real-time Reporting

Get suite execution results in real time. There is no longer a need to wait for the entire suite to complete execution. Our real-time reporting portal shows the execution results of multiple suites being executed in parallel by CI tools. 

How Does it Help?

• Reduced Wait-time for Analysis: The automation cycle is often delayed because execution results of long running test suites with multiple test cases is only available when the entire execution is complete. Qualitia provides real-time reports for each test case immediately. Now analyse defects/failures as soon as the test case is executed.

• Compatibility with Browsers: Our real-time execution results can be seen across all widely used Web browsers. 

• Storage of Screenshots and Logs: Capture, compress and store screenshots and logs associated with test executions, so that they can be stored and transmitted.

• Pinpoint the Failures with Analysis: Traverse through the execution results to find and analyse points of failures and defects. This makes it easy to understand and troubleshoot issues efficiently.

For more information, refer to Real Time Reporting Portal .

Executions on Remote and Cloud Environment through Qualitia Client

In addition to executing test cases on remote and cloud environments using the offline package, you can now execute test cases on remote and cloud environments right from the Qualitia Client.

Qualitia supports the following cloud environments:

• Saucelabs

• Browserstack

• Perfecto

• Testobject

For more information, refer to Supported Environments and Guidelines .

Execution Profile

An execution profile lets you define a set of configuration settings for test suite executions. You can add multiple execution profiles with different combination of configuration settings for different environments.
Having execution profiles in place saves you a lot of time that you spent on changing the configuration settings for every execution manually.

For example, earlier even to switch to another browser for a test suite execution you had to manually change the settings. Now you can create multiple execution profiles for different browsers and simply select the one that you want to use during test suite execution.

For more information, refer to Working with Execution Profiles.

Configuration Settings

You can now configure settings on project level depending on the project requirements. This comes handy in situations where you can choose whether or not you want to integrate your project with version control tools, such as GIT or SVN.

For more information, refer to Configuring Qualitia Settings .

Offline Configuration Utility

The Offline Package now includes the Offline Configuration Utility, which makes changing configuration settings for offline execution and offline package execution very easy. You are no longer dependent on the CLI command extension tools to modify configuration settings or execute the offline packages.
Additionally, if the offline package is configured and connected with the Qualitia Server during execution, you can track the suite executions in the Real Time Reporting Portal.

For more information, refer to Offline Package.

Server Upgrade Process

If you upgrade to Qualitia 8.x.x from a previous version, if a few projects fail, you are required to only restore the backups of the failed projects. The Upgrade program is now enhanced to save your time by not having you to restore the passed projects.

For more information, refer to Upgrading Qualitia Server and Client.

Healthcheck utility

This release introduces the Health-Check utility that lets you check the health of the Qualitia Server and Qualitia Client components. The Health-check utility can perform both the pre-installation and post-installation checks.

• Pre-installation checks: Verifies if your computer meets the minimum system requirements to install the Qualitia Server or the Qualitia Client.

• Post-installation checks: Verifies if all the components of the Qualitia Server or the Qualitia Client are installed and functioning properly.

For more information, refer to Qualitia Healthcheck Utility.

Qualitia Licensing and Authentications

The following changes are made for licensing and authentications:

• There’s no separate ALM license anymore.

• If the Qualitia client crashes, then after a few minutes, the license is released.

• Earlier licensing was a session-based, now licensing is login based.

• Now only the Qualitia server communicates with the Qualitia License server to fetch licensing details. Earlier, each Qualitia Client and Qualitia License server used to communicate with each other.

For more information, refer to https://qualitia.atlassian.net/wiki/spaces/QAS/pages/1718944185.

Dropped features

The following features have been dropped in this release:

• Debugging is not supported.

• Student Edition is discontinued.

• Integration with Defect Management system is unavailable.

Bug Fixes and Enhancements

The following are the details of bug fixes and enhancements made in this release:

• Even if you do not specify browser driver path, Qualitia would install and download the browser driver path while execution.

• Every Qualitia Client is bundled with Appium for mobile application testing.

• During a hybrid test case execution, you can switch from native environment to a web page view using a single Mobile.StoreWebViewHandle action. Earlier, to do this, you had to use the following two actions in the sequence listed: 

  • Mobile.StoreWebViewHandle 

  • Mobile.SelectWebView 

Known Issues

The following are the known issues in Qualitia Automation Studio 8.0 Beta release.

Qualitia Automation Studio Recorder

Qualitia Web Recorder

• The Pause/Resume and Stop button do not work from the Qualitia Editor. As a workaround, use the Pause/Resume and Stop buttons of the Qualitia Web Recorder to pause or resume, or to stop the recording.

• Qualitia Web Recorder may sometimes not record the objects on a popup. To work around this issue, verify if the steps are recorded, if not, try recording them again.

• By design, the recorder does not start until all the objects on a web page are loaded. Ensure that all the objects on a web page are loaded before you start recording.

• Recording keyboard interactions are not supported in this release. As a workaround, you must add such steps manually in the Qualitia Editor.

• Recording objects on Windows dialog boxes, such as downloading or uploading files, or entering user credentials, is not supported in this release. As a workaround, add these steps manually in the Qualitia Editor.

• While recording a web application, if you press Alt+Tab from the keyboard, it is added as Alt+Left in the parameter. You must remove such unnecessary steps captured by the recorder in the Qualitia Editor.

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

• Qualitia Web Recorder does not support Shadow DOM.

• While recording a web application, if you click the play or pause button of a video, it is not recorded as a step. As a workaround, you must add these elements manually in the Qualitia Editor.

• Qualitia does not recommend using the recorder during dry runs. However, if you do so you may face issues and see unexpected results.

• While recording a web action, if you click Back and Forward buttons, they are not recorded as steps. You need to enter steps manually with actions as NavigateBack and NavigateForward.

• While recording a web application, alert actions are not recorded. You must add these actions manually in the Qualitia Editor.

Qualitia Mobile Recorder

• The Pause/Resume and Stop button do not work from the Qualitia Editor. As a workaround, use the Pause/Resume and Stop buttons of the Qualitia Mobile Recorder to pause or resume, or to stop the recording.

• While recording a mobile application, if you disconnect a physical mobile device, the application session continues. To work around this issue, restart the agent and reconnect the mobile device to start recording.

• You cannot record ClearText messages on iOS devices. You must add such actions manually in the Qualitia Editor.

• While recording an iOS application, if you click the keys of the soft keyboard, every keystroke is recorded as a step. You must not use the soft keyboard to enter values, use SetText mode to enter the values. To clear the texts, you must pause the recording session and use soft keyboard to remove the text from the mobile.

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

• When recording a mobile web application on iOS simulator, it opens a blank browser. As a workaround, enter the application URL manually and refresh the browser to fetch the latest objects.

• Qualitia Mobile Recorder does not support iOS version 12.0 or above for mobile web recording and web view context of a hybrid application.

• Qualitia Mobile Recorder does not support flick gesture. You can use swipe gesture instead of the flick gesture.

• Qualitia Mobile recorder does not support entering values on objects from a keyboard. You need to enter values using SetText and ClearText modes.

• While recording a mobile web application, if you switch between multiple tabs on a mobile browser, it is not recorded as a step. As a workaround, for the switch window step, you must manually add a step with selectwindowusingurl as the action and the window URL as the parameter.

Reports and Dashboards

Realtime Reporting Known Issues

• The Real Time Reporting portal and Reports tab of Qualitia client does not display the test cases executed through TFS/Azure DevOps and HP ALM. Currently, you need to view the associated test suite executions reports in TFS/Azure DevOps and HP ALM only.

• While a test suite execution, Qualitia does not display any appropriate alert message if the Qualitia Server does not have the required space. As a result, you might not view the suite execution report.
  The Admin needs to monitor the amount of available space in Qualitia Server regularly and remove the reports data that are no longer required from the Server Administration Portal. For more information, refer to Purging the Reports Data.

• Qualitia allows you to edit a text for a test case step under the Name/Condition column in the test case editor screen of the Qualitia Client and save the test case. However, after executing the associated test suite, the suite execution report screen displays the original text 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 resolution lower than 1100px.

• Real Time Reporting portal does not restrict the status bar and log icon moving out of the visible window, which might result in losing them. As a workaround, you have to refresh the report page to display the status bar or log icon.

• Due to a known Firefox bug, the Real Time Reporting portal does not display the white borders in table grids in the Firefox.

• Export to Excel feature currently does not support export the Qualitia Design Studio related attributes such as Module, Epics and Stories for a QDS enabled project 

• Real Time Reporting Portal shows the browser version used for test suites executed on mobile web applications intermittently. As a workaround, before a test suite execution, you need to specify the browser version in the Edit Desired Capabilities of the associated execution profile.

Dashboard Known Issues

• The Defects logged report and Trends chart would not display any data as Qualitia v8.0.0 Beta does not support Manual nor Auto-defect creation.

• The Suite Execution Time statistics chart may show a difference of a second in the Average execution time metric due to rounding of milliseconds to seconds.

Old Qualitia Reports

• Export to Excel feature is not available for reports of executions prior to release 8.0.0, that are viewed from the Show Old Reports menu.

Cloud Executions

Perfecto

• Desktop web executions are not tested on Macintosh computers. 

• The mobile native and hybrid application file (i.e. apk/ipa/app file) is not uploaded on Perfecto automatically during the Qualitia Automation Studio executions. Hence, the operation to upload the application file to the Perfecto repository is disabled in this release. 
  As a workaround, manually upload the application file to Perfecto. For more information, refer to the URL: 
  https://developers.perfectomobile.com/display/PD/Upload+Item+to+Repository 
  Note: After you upload the application file to Perfecto, ensure that you set Perfecto lab repository path as the first parameter of the Mobile.OpenApp action. For example, Perfecto lab repository path: "PRIVATE:MyApp.apk".

Sauce Labs

• Mobile executions with iOS mobile native and hybrid applications are not tested. iOS application testing on Sauce Labs simulators was not possible due to technical difficulties with Sauce Labs.