What’s New in Qualitia Design Studio 2.1.1
Enhancement
Error handling of the functionality has improved due to which QDS now allows multiple users to integrate with Jira Setup on the same project simultaneously.
Bug Fixes
Fixed minor issues in UI to improve user experience.
What’s New in Qualitia Design Studio 2.1.0
New Features:
Synchronization with Desktop Projects of Qualitia Automation Studio
You can create a desktop project and sync with a Qualitia Automation Studio desktop project.
Displays the DP and OR objects in read-only mode, which are created in the associated Qualitia Automation Studio project.
You can filter objects based on the project types
Changes in objects management for performance improvement
Applicable to both Desktop and Web/Mobile projects:
The object list is paginated.
The searching of objects is enabled with pagination and hierarchy information.
You can filter objects for specific projects.
You can search the objects from the test case and task editor screens.
Applicable to Web/Mobile projects only:
You can search for parent objects while creating or editing objects
Known Issues:
QDS does not allow multiple users to integrate with Jira Setup on the same project simultaneously. This issue will be fixed in the upcoming release.
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 and does not allow you to edit or save the test case in QDS.
To work around the issue, perform the following steps:Export the test data of the affected test case. This allows you to use the test data partially again.
Detach all the tasks and remove all the TC steps from the Test Case in QAS.
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.
Objects created in desktop projects of Qualitia Automation Studio may fail to sync with Qualitia Design Studio.
QDS does not display the mobile objects having UIAutomator LocatorType. Hence, while using MOS or Qualitia Automation Mobile Recorder, in the LocatorType precedence settings, set UIAutomator to lowest. Also, replace the LocatorTypes of the objects having the UIAutomator LocatorType with another LocatorType.
What’s New in Qualitia Design Studio 2.0.1
Minor Bug Fixes
Some Design Changes
What’s New in Qualitia Design Studio 2.0.0
Measuring Test Case Coverage for User Stories
You can define acceptance criteria for user stories and get it reviewed from team members. For more information, refer to Measuring Test Case Coverage for User Stories.
For more information, refer to Measuring Test Case Coverage for User Stories.
Granting Review Privileges to Users
Admin can grant review privileges to users to review specific epics.
For more information, refer to Granting Review Privileges.
Configuring the Project Level Setting to make “Review Acceptance Criteria” mandatory
When a project manager or admin configures the setting to make review acceptance criteria mandatory, its test cases cannot be shared for Automation until their acceptance criteria are approved.
Baseline Release
This allows users to map their on-going release in QDS project so that they can view the test coverage for the current release.
Enhancements in End-to-End Traceability
You can view the latest execution status for all the test cases that are shared for automation. Also, you can know the date and time and the associated test suite name for the latest test case execution.
Bug Fixes and Enhancements
Minor bug fixes
New Theme Design
Known Issues
Latest execution status of the test cases does not consider executions through TFS/AzureDevops and HP ALM.
Users can create only one Baseline release for a QDS project.