Page History
...
| Info | ||
|---|---|---|
| ||
Defect issues can also be covered by Test cases just like Requirements. In this case, the defect issue types (e.g. Bug) must also be mapped as a Requirements issue types in Xray global configuration. |
How to cover a Requirement
...
- Associate Tests or Test Sets (using the Xray issue picker)
- Associate Tests or Test Sets (using plain Jira issue Links)
Create Tests
This action allows you to access the create issue dialog, with some preset field values such as "Test" issue type and link to the requirement issue.
Associate Tests or Test Sets (using the Xray issue picker)
This option allows you to create Jira issue links between the Requirement and Test or Test Set issues thus covering the requirement with Test cases.
This operation can be performed using the Issue Picker Dialog which allows you to search, and select multiple issues to link with the Requirement. JQL searches are also possible. This dialog replaces the native Jira issue link dialog making it easy to associate Tests (or Test Sets) with requirement issues.
Associate Tests or Test Sets (using plain Jira issue Links)
...
Step 2: Select More > Link. The Link screen will appear.
Step 3: On the This issue field, select the tested by option.
...
- Input the desired Test/Test Set Issue Key on the Issue field;
- Click on the Down Arrow on the Issue field and select the Test 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 issue view screen
...
Step 2: Select More > Link. The Link screen will appear.
Step 3: On the "This issue" field, select the "tests" issue link type.
...
- 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.
Tests data table
...
The Basic mode has a set of default fields but you can also search and select other fields from the More option.
Advanced
The Advanced mode allows you to search based on a specific JQL.
Summary view
The summary view presents the field names and values applied in the active filter. When these exceed the available space "..." are added and all information is visible in the tooltip.
Sorting
The list can be sorted by the columns you can add or remove to and from the list using the Columns dropdown menu.
| Info | ||
|---|---|---|
| ||
The list sort criteria is kept in user preferences. |
...
| Columns can be quickly added to the list using the columns search, this allows to locate and select the desired field(s) in a practical manner. | Columns can also be quickly removed from the list using the Restore Defaults link or by unselecting the undesired field(s). |
|
|
| Info | ||
|---|---|---|
| ||
The changes made to the selected columns are kept in user preferences if you wish to change the defaults those are set in Xray Administration > Default Column Layouts under the Test Coverage Columns field. |
...
A linked test can be removed directly in the test coverage list using the following operations:
Inline remove
A confirmation message is always presented. When the selected test was added via a Test Set link, it cannot be removed separately, so by confirming the operation, the test set link to the requirement as well as the links to all the tests it includes will be removed.
Bulk selection for removal
A confirmation message is always presented. When within the selected tests, are tests that were added via a Test Set link(s), they cannot be removed separately, so by confirming the operation, the test set link(s) to the requirement as well as the links to all the tests they include will be removed.
Analyzing Test Coverage
...
Once the analysis scope is changed, the status is automatically recalculated for the new scope. The status of the Tests within the data table will also be affected by the selected analysis scope.
| Info | ||
|---|---|---|
| ||
The user analysis scope preferences are kept, per project and based on the last configuration. |
...
When the analysis scope is set per version it allows you to see the Requirement status for each project´s version.
Test Plan
When the analysis scope is set per Test Plan it allows you to see the Requirement status for the selected Test Plan.
Environments
The statuses presented in the context of an analysis scope also depend on the Environments.
Therefore you can see both the requirement status and the test statuses based on the combination of scope and test environment you have selected.
Test Runs
The Test Runs column will present the link to the Test Run affecting a particular status of a Test.
...
The user can then click on the Test Run to go to the execution page.
| Info | ||
|---|---|---|
| ||
For more details, please check the Coverage Analysis page. Here you can find all the areas where you can take advantage of the coverage analysis such as the entities (Requirements, Tests, Test Sets) and also reports. Also, make sure to check the Understanding coverage and the calculation of Test and requirement statuses TTT article if you need to learn how is the Coverage status calculated in more detail. |
Creating Test Execution / Sub-Test Executions
This action allows you to create a Test Execution (1) or a Sub-Test Execution (2) with some preset field values such as the links to all the tests currently covering the requirement issue. You can also create a Test Execution/Sub-Test Execution with a subgroup of the tests based on their status (3).
This action is useful if you create one Test execution per Requirement issue. Working in an agile context, this is a usual pattern. If you are using Scrum or Kanban boards in Jira, creating Test Executions / Sub-Test Executions allows the Tests to be just another work item for a given Requirement.
