Page History
...
| Gliffy Diagram | ||||
|---|---|---|---|---|
|
Don't mix my Requirements and Defects with Tests
If you already have a Jira project for managing Requirements and Defects and don't want to have any tests nor executions in this project, you can create a separate companion project just for testing purposes.
| Gliffy Diagram | |||
|---|---|---|---|
|
...
|
Tests Dedicated Project
Another common use case for Xray is to have a dedicated project for Test (and Pre-Condition and Test Set) issues; sometimes, referred to as a Tests repository. Test Executions are the responsibility of other project(s). This separation allows to manage permissions more effectively, so maybe only a few testers have permission to write tests and others only have permission to execute.
Of course, this use case can also be combined with the previous one by having separate projects for managing Requirements and Defects.
Gliffy Diagram
| Tip | ||
|---|---|---|
| ||
If you plan to have separate projects for managing Requirements/Defects and Tests Executions and you want to analyze Requirements by version, then your Requirement's project version names must match the names of the Test Execution's project. This is how to do it. |
...
In this use case, the Tests, Requirements, Executions & Plans and Defects all separated and being handled on different projects.
| Gliffy Diagram | ||||
|---|---|---|---|---|
|
Isolated repository for Tests
In this more uncommon scenario, you would have your requirements outside of Jira in some other tool. You use Jira only as a test testing repository for creating Tests, Test Sets, Test Plans and Test Executions.
You can use Xray for this, but you will lose the benefits of requirement coverage and traceability.
| Gliffy Diagram | ||||
|---|---|---|---|---|
|
| Info |
|---|
Users implementing this scenario might gain huge benefits if they are able to synchronize requirements between the other tool and Jira. |
...