...
| Terms | Description | |||||
|---|---|---|---|---|---|---|
| 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 rulesacceptance criteria. | |||||
| Acceptance Criterion (also known as Business Rule (BR) | A business rule An acceptance criterion is an aspect of the functionality or the part of the functionality being tested. A Business Rule It 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 ruleacceptance criterion. One or many activities within a business rule a acceptance criterion 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.
|