Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

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. 


Points to Know

  • You can integrate a QAS project with a single QDS project only and vice-versa.
  • 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.
  • One Design Studio project can be mapped to one automation studio project only.
  • In case you are using Bitbucket (GIT) as version control, first create a project branch in the Bitbucket repository and then create project from Qualitia.
    For more information about creating a branch in Bitbucket repository, refer to the links mentioned below:

In this section:

  • No labels