Page History
...
A Requirement represents a singular documented physical and functional need that a particular product or process must be able to perform. They are also an important input into the verification process, since tests should trace back to specific requirements, showing what elements and functions are necessary for the particular project. Most of the times, Requirements are the only coverable/testable entities. For the purpose of this page, whenever talking about Requirements please consider that we're referring to Coverable Issue types, as defined in Project Settings: Test Coverage.
A Defect represents a condition in a software product which does not meet a software requirement (as stated in the requirement specifications) or end-user expectations (which may not be specified but are reasonable). It can be displayed as an error, flaw, failure, or fault in a computer program or system that produces an incorrect or unexpected result, or causes it to behave in unintended ways.
These two concepts can be mapped to different issue types in organizations.
| Info | ||
|---|---|---|
| ||
A testable/coverable entity typically corresponds to requirements. However, it's possible to cover and validate any issue type as long as it is configured as being a Coverable Issue Type in Project Settings: Test Coverage. |
| Gliffy Diagram | ||||
|---|---|---|---|---|
|
Often, a Defect issue type is also used configured as a Requirementtestable entity. 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 being Coverable and as being a Defect. So, a Defect can also be associated with Test issues and be considered for Requirement Test Coverage charts and Custom Fields.
Requirements and Defect issues can be associated with Tests and Test Set issues with the Jira default linking mechanism. There are specific issue link types for associating these issue types:
...