Design studio helps in getting a clear understanding of the requirements to automation testers before they actually start testing the application. This develops highly scalable and maintainable test automation design, which gives end-to-end traceability from requirements to automation test cases.

Qualitia Design Studio allows creating manual test cases to validate requirements depicted under epics and stories. After you complete working on these requirements, these manual test cases can be synchronized to Qualitia Automation Studio so that automation tester can create automation scripts.

Before you Begin

You must know the following points for the QDS integrated projects:

You can integrate a QAS project with a single QDS project only and vice-versa.
You can integrate with a QDS at the time of creating a QDS project only.
Ensure that your associated role is assigned with the Test Development privilege.
The Development section has Requirements screen instead of Test Case Editor screen. The Requirements screen has all the functionalities of Test Case Editor screen and other feature related to synching and sharing with the associated QDS project.
You cannot use the Import Task feature to import tasks from another project.
You cannot create test cases in QAS. You need to create test cases in QDS, and then Share for Automation, after which only you can edit or remove test cases.
While creating a new project Qualitia syncs all the existing objects along with the tasks and test cases that are shared for automation in Qualitia Design Studio. Once synced, objects can be edited or deleted in automation studio only.
Test cases and tasks can be accessed only after they are shared for automation from Design Studio.
In case you are using Bitbucket (GIT) as version control, first create a project branch in the Bitbucket repository and then create the project in QAS.
For more information about creating a branch in Bitbucket repository, refer to the links mentioned below:
- If you are using Git bash, click here.
- If you are using SourceTree, click here.

In this section:

Browser not supported