Page History
Table of Contents |
---|
Definition
...
Gliffy Diagram | ||||
---|---|---|---|---|
|
Often, a Defect issue type is also used as a Requirement. To assert that a Defect does not occur again, it can be also considered for testing. Xray allows the same issue type to be mapped as a Requirement and a Defect. So, a Defect can also be associated with Test issues and be considered for Requirement Coverage charts and Custom Fields.
...
Gliffy Diagram | ||||
---|---|---|---|---|
|
Info |
---|
Customizing the "Tests" Issue Link Type: During the installation of Xray, the Issue Link Type "Tests" that is used in the associations between Tests/Test Sets and requirements is automatically configured. You can customize the default name, outward and inward description of this Issue Link Type, but after that, it is required to disable and then enable the add-on in the 'Manage add-ons' page. Issue link "Test" has by default "tests" and "tested by" as outward and inward descriptions, respectively. If you decide to downgrade to a version <= 3.0.x, make sure you restore the default Issue Link Type names and descriptions; otherwise Xray will create new Issue Link Types. |
Sub-Requirements
A requirement can be associated with sub-requirements, resulting in a hierarchy of requirement issues. "Epic" requirements can thus be decomposed into smaller requirements, each associated with specific tests. This decomposition of requirements facilitates the management of epic requirements and makes their coverage analysis easier.
...
Gliffy Diagram | ||
---|---|---|
|
|
|
Info |
---|
For more information on Requirement Status and coverage, please go to the Requirements Coverage Analysis page. |
Associating a Requirement
...
- Input the desired Requirement Issue Key on the Issue field;
- Click on the Down Arrow on the Issue field and select the Requirement from its History Search list;
- Click on the search for an issue link to use the Find Jira issues browser;
Step 5: Click Link.
From the Test Set issue view screen
...