Versions Compared

Old Version 51

changes.mady.by.user Shruti Agrawal

Saved on

compared with

New Version Current

changes.mady.by.user Shruti Agrawal

Saved on

Key

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

We are thrilled to announce the release of Qualitia Automation Studio (QAS) - 9.0. In this section, you will find information about the new features incorporated into the QAS 9.0, as well as details regarding enhancements, bug fixes, and known issues.

Release Notes for September Release (Build 9.0.4166)

Highlights

  • Single Sign-On (SSO) Integration:
    Qualitia now supports Single Sign-On (SSO), simplifying user authentication and enhancing both security and user experience.

    • Enhanced User Experience: SSO enables users to log in once and access Qualitia and other integrated applications with a single set of credentials, reducing multiple logins and saving time.

    • Improved Security: Centralized authentication through SSO enforces stronger security measures such as multi-factor authentication (MFA) and robust password policies, reducing the risk of security breaches.

    • Seamless Access to Integrated Tools: SSO allows smooth transitions between different applications for testing, development, and reporting, improving productivity without the need for repeated logins.

    • Compliance and Auditing: SSO helps organizations meet compliance requirements by centralizing user access controls and offering detailed audit logs of authentication activities, aiding in regulatory compliance.

...

  • Live Report Disabled During Execution & Not Visible on Real-Time Reporting Portal: If the Live Report option is disabled and execution is not visible on the Real-Time Reporting portal, check the disk space—it should be at least 10%. To temporarily resolve this, update the
    C:\ProgramData\Qualitia Automation Studio - Server\workspace\data\settings.yaml
    and set the appropriate limit.

  • A blank window may appear during offline headless execution when using Chrome browser version 129.

  • For ADO mobile execution, capabilities must be manually added in the ADO pipeline. For more details, refer to https://qualitia.atlassian.net/wiki/spaces/QASNew/pages/34857454550/Azure+DevOps+Integration#%F0%9F%94%A7-Got-a-problem%3F-Let%E2%80%99s-fix!.

  • Atlassian has officially revoked support for Jira on-premise installations. As a result, Jira on-premise is no longer supported for integration with Qualitia. Users attempting to integrate Jira on-premise with Qualitia may encounter functionality issues or failed integration attempts.

  • After migrating data from version 8.x, executions may not appear in the Real-Time Reporting portal. This issue arises when the dashboard was disabled in Qualitia v8.x. For more details, refer to https://qualitia.atlassian.net/wiki/spaces/QASNew/pages/34857453641/Real-time+Reporting+Portal#%F0%9F%94%A7-Got-trouble%3F-Let%E2%80%99s-fix!.

  • When a Salesforce object is deleted and recreated with the same name without accepting changes through Change Management, a uniqueness conflict may occur. Since the label is used as the unique identifier for Salesforce objects, the new object will retain the same Object ID as the previously imported object in Qualitia, potentially leading to issues in object management and identification.

  • Applications that restrict taking screenshots or screen recordings will not support live streaming for Mobile ObjectSpy and Mobile Recorder. This limitation affects the ability to capture or broadcast content from such applications within these features.

Fixed Issues

  • Fixed the issue where after completing the Qualitia installation and license key deployment, an error occurred while loading a project in the Project tab. This issue has been observed under specific conditions. For more details, refer to https://qualitia.atlassian.net/wiki/spaces/QASNew/pages/34857452383/Project+Creation#%F0%9F%94%A7-Got-Trouble%3F-Let%E2%80%99s-Fix!.

  • Fixed an issue where the value "$NULL$" was not being recognized as an empty string, causing execution failures.

  • Addressed a bug preventing users from expanding or collapsing task steps in the debugger after an upgrade.

  • Resolved an error encountered when creating a new project in an upgraded sandbox environment, which previously resulted in a "project setup failed" message, blocking access to other working projects.

  • Fixed the issue where Salesforce connections were removed from Settings after an upgrade, and previously imported objects were no longer visible in the Objects Repository section.

  • Resolved the issue where test cases containing the waitForVisibility action failed to execute. Support for the waitForVisibility action has been reintroduced, fully addressing the execution problem.

  • An issue causing Qualitia to crash when loading existing test cases has been resolved, ensuring smoother performance and stability during test case loading.

Release Notes for August Release (Build 9.0.3835)

...

  • The Scheduler execution is not working on Safari browser due to failure of Webdriver object creation.

  • When you create a new connection using the Salesforce application and try to import objects, you may see additional object entries under the Import Object section.

  • Not be able to load the SFDC project after an upgrade: If you are not able to load the SFDC project after an upgrade to Qualitia’s latest version, you need to delete the Workspace folder. You can find the workspace folder on the below path: C:\Users\user1\AppData\Local\Qualitia Automation Studio - Client\workspace.

  • Newly added objects are not visible on Import model: If you are not able to find a newly added object on the import model, while creating an object create it as mandatory and save. Once the object is saved, make it non-mandatory, as only mandatory fields are visible on the Import modal. This will make the object visible and ready to be used.

  • Getting error "Early EOF" while project setup after replacing the server workspace: You might get this error while project setup if the credentials through which the VM was logged-in is different from which the Web Services were started. To avoid getting this error you have to make sure that the same log in credential is used for VM as well as web services. To fix this error, refer https://qualitia.atlassian.net/wiki/spaces/QASNew/pages/34857452383/Project+Creation#%F0%9F%94%A7-Got-Trouble%3F-Let%E2%80%99s-Fix!

  • Error while fetching objects for connection: If you are getting the error message Error while fetching objects for connection, while importing the objects, make sure to enable the Client credential flow on the Connected App.
    Note: You can also connect using OAuth Client Credential to avoid such errors.

  • Mobile test case execution is failing on ADO: To execute mobile test cases successfully on ADO, you need to provide all the mobile capabilities manually. Please refer https://qualitia.atlassian.net/wiki/spaces/QASNew/pages/34857454550/Azure+DevOps+Integration#%F0%9F%94%A7-Got-a-problem%3F-Let%E2%80%99s-fix! for detailed steps on how to add mobile capabilities.

  • Scheduler execution is not working when there is more than 1 test case giving error "ALL TC ITERATIONS MARKED FALSE".

Relase Notes - Qualitia Automation Studio - 9.0 (

...

Build 9.0.3422)

What’s New

🚀Getting Started

...