Before getting started, let us have a look at the common terms that you will come across when using Qualitia Design Studio.
| Terms | Description |
|---|---|
Qualitia Design Studio | |
| Project | A JIRA project is a collection of issues. The team can use a JIRA project to coordinate the overall development of the product, track it from time to time, and more, depending on your requirements. A JIRA project can also be configured and customized to suit the needs of individuals or teams. |
| Epic | An epic is a large body of work. It is essentially a large user story that can be broken down into a number of smaller stories. |
| Story | A story or user story is the product requirement expressed in a few short sentences, ideally using non-technical language. A story may have one or more business rules. |
| Business Rule (BR) | A business rule is an aspect of the functionality or the part of the functionality being tested. A Business Rule is intended to assert business structure or influence the behavior of functionality being tested. |
| Activity | An activity is a complete set of tasks. Multiple tasks can be performed to complete an activity. |
| Steps | A Step is a basic unit of a task to be performed to complete the activity. A task is created by combining multiple steps. |
| Precondition | This option notifies the existence of any condition prior to evaluating the business rule. One or many activities within a business rule can form a precondition. Selection of this check box notifies the user about the mandatory requirement of precondition. |
| Qualitia Automation Story | Selecting this option makes this story available in Qualitia Automation Studio for Synchronization. Once synchronized, test personnel can start developing test cases to be executed using Qualitia Automation Studio. |
Qualitia Automation Studio | |
| Unmapped | Test cases which were once the part of Epics and Business Rules are moved to the unmapped section once their activities are removed from the Qualitia Design Studio. |