Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
UI Steps
UI Step



The “latest”/consolidated status of the coverable issue (e.g. requirement) for a specific context

  • Depends on where/how you’re analyzing your ”requirement"
  • Generally, it represents the latest result obtained for that Test in that context
  • More grained or high-level overview
  • Can involve consolidating results from multiple Test Environments
  • e.g. status of a Test for version 1.0, depends on consolidating the latest results for Chrome and Firefox




Info

the “Requirement Status” custom field provides a sneak peek for it (explained ahead)




UI Step

Where is it present 

Overall Requirement Coverage (indirectly)Requirements List gadgetTraceability report

Image Modified

Image Modified

Image Modified

UI Step

How and issue/requirement can be covered

UI Step

Understanding Sub-requirements

Image Modified

Image Modified

Image Modifiede



UI Step

Requirements Hierarchy


Xray fully supports two level of requirements

  • Traceability and Overall Coverage Reports/gadgets are limited to two levels

  • It is possible to have more levels using one of the following combinations (although this hierarchy won’t be fully visible throughout Xray)
  • Epic⬄Story relation + specific issue link
  • Epic⬄Story relation + sub-task issues


Image Modified

Image Modified

Info

Coverage - Which Tests are considered?

By default, the list of Tests that cover an issue/requirement is not dependent on the version, i.e. all “linked” Tests are considered

If you wish to control which Tests are ”valid” for each version, then you must choose the Use versioned Test Sets for Requirement Coverage” in the Requirement Coverage Xray settings

  • For each version, you must create a Test Set and assign it to the version you want, and only those Tests will be considered for the coverage calculation
UI Step

Coverage Status – Simplified overview​


  • OK  All the tests associated with the issue (e.g. requirement) are PASSED 
  • NOK At least one test associated with the issue is FAILED
  • NOT RUN  At least one test associated with the issue is TODO, ABORTED  or EXECUTING and there are no tests with status FAILED
  • UNKNOWN  At least one test associated with the issue is UNKNOWN and there are no Tests with status FAILED
  • UNCOVERED The issue has no tests associated to it

Image Added

UI Step

Calculation of coverage status in given scope


  1. Obtain the list of Tests that cover the issue, directly or indirectly through sub-requirements
    1. Depends on the Coverage configuration in the Xray settings
  2. Calculate the Test status for all the Tests individually, in the given scope
    1. Considers Test Runs in version V (as a result of Test Executions in version V) or Test Runs in Test Plan TP (within Test Executions associated with Test Plan TP)
    2. If a specific Environment is also chosen, then only Test Runs from Test Executions with this Environment will be considered. In case no Environment is specified then all Test Executions are considered
  3. Calculate the coverage status mapped to the previously calculated Test statuses
  4. Compare the previously calculated coverage statuses together