Versions Compared

Old Version 2

changes.mady.by.user Sofia Canario

Saved on

compared with

New Version 3

changes.mady.by.user Sofia Canario

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

UI Steps
UI Step

Review Default Coverage Settings for Requirement Coverage Strategy

Go to JIRA Administration > Manage Apps > Xray > Requirement Coverage.

By default the requirement coverage strategy uses versioned test executions, this means that the requirement status (OK, NOK, UNCOVERED, UNKNOW, NOTRUN) can have different statuses for each version.


The alternative is to use Test Sets, instead. This is a more complex approach because Tests need to be associated with Test Set for a specific version. 


UI Step

Review default settings for the relation between Test status and Requirement status

Go to JIRA Administration > Manage Apps > Xray > Requirement Coverage.

By default, the result of a Test will affect all Requirements that are associated with it. 



The alternative is to allow the users to manually set Requirement status for each Test Run during the execution. This is suitable to for more complex scenarios but means that your users have to set requirement statuses manually . 

UI Step

Check other Coverage Settings 

The remaining coverage settings 

Include Previous Version Requirements

When this option is checked, the option to include all Requirement issues of previous versions in Requirement Coverage charts will be checked by default.

Requirement Coverage Strategy

The requirement coverage strategy defines how the Requirement Status must be calculated. The following strategies are available:

Use versioned Test Executions for Requirement Coverage

When this option is enabled, the Status of a Requirement for a specific Fix Version V is calculated based on the latest Test Run with Fix Version V of each associated Test. With this strategy, a Requirement can have different Statuses one for each Fix Version in the project.

Use versioned Test Sets for Requirement Coverage

When this option is enabled, Requirement Tests must be associated with Test Sets of a specific Fix Version to be considered for the Requirement Coverage of that particular version. A given Test T is considered for requirement coverage of Requirement R in the version V if:

  • T is associated with R
  • T is associated with any Test Set with version V

Once Test T is considered for coverage in version V, its Status is calculated based on the latest Test Run with the specified Fix Version V.

Learn more

Please see more info in the page dedicated to Coverage Analysis in the User's Guide.

Ignore Requirements with Status

Choose the workflow statuses for which the Requirement issues will not be included in Requirement Coverage Charts.

Ignore Requirements with Label

Choose the labels for which the Requirement issues will not be included in Requirement Coverage Charts.

Ignore Tests with Status

Choose the workflow statuses for which the Test issues will not be considered when calculating the Requirement Status, even if they are associated with Requirement issues.

Requirement Historical Chart Days

Specifies the default number of days that the requirement coverage historical chart must display when opened.

Separation of Concerns

When this option is checked, the result of a Test will affect all Requirements that are associated with it. Uncheck this option if a single Test result affects multiple Requirements in different ways and these might have different statuses depending on specific steps. This will allow you to manually set the affected Requirement statuses for each Test Run on the execution screen. The calculation of the Requirement Status will then consider these Requirement statuses explicitly. 

Example

Test T1 is associated with Requirements R1 and R2: 

  • Checked: If the latest execution result of T1 has FAILED then both Requirements are NOK.
  • Unchecked: If the latest execution result of T1 has FAILED and this could only affect R2, then R1 can be OK and R2 is NOK.

Include Previous Version Requirements

the test execution screen. By unchecking this option you will get a new section in the execution screen to select the status of the affected requirements. 


Image Added



UI Step

Review default settings for Test workflow status 

Go to JIRA Administration > Manage Apps > Xray > Requirement Coverage.

By default, all tests linked with a requirement are considered in the requirement status calculation. 

Image Added


The alternative is to ignore some tests, depending on the workflow status that they have. For example, you may want to ignore tests that are in the workflow status "waiting for approval". This is suitable to more complex scenarios, where you have test specification lifecycle managed by a Jira workflow. 

Info

The remaining settings available at "Requirement Coverage" are related with to how / what information should be displayed in reports related to coverage. 

Check documentation if you want to explore those settings

...

.