Page History
...
Agile boards are great, but they do not replace other types of reports where more information may be consulted and analyzed.
Table of Contents |
---|
Using Xray issues in Agile boards
Since Xray uses Jira issue types for most of its entities, in theory, you're able to include them in your boards. However, the reason may be different for each one of them.
...
Use case | Notes | |
---|---|---|
Test |
| |
Pre-Condition |
| |
Test Set |
| |
Test Execution |
|
|
Sub Test Execution |
|
|
Test Plan |
|
|
Configuring Agile Board (Active Sprint and Backlog)
In order to make sure that only the relevant issues appear (e.g. Stories, Bugs, Test Plans and not Tests) in the Backlog and in the Active Sprint, you need to configure the Board properly.
...
You need to go Board > Configure.
Then, choose General and edit the Saved Filter.
The Update the query of the saved filter filter to contain the relevant issues.
The exact filter to use depends on the issue types you have on your project; a possible filter could be:
...
project = CALC AND issuetype in (Story, Epic,Bug, Task,"Test Plan", "Test Execution", "Sub Test Execution") ORDER BY Rank ASC
Usage scenarios
A typical concern with Agile boards is having them as clear and as "non-polluted" as possible, so you can focus on what's important.
...
Next, you may find some possible scenarios for integrating testing into your Agile boards, although you're free to adapt each one to your needs.
Requirement Status on Agile Board
You can add the Requirement Status custom field to the requirement issues in the Active Sprint. It’s actually a useful feature provided by Jira. It gives you the ability to add custom fields in both views: Active Sprint and Backlog. Adding certain Xray custom fields, such as the Requirement Status, may be a good for your testing teams because it provides a quick overview of the current statuses of the requirement issues.
...
As a suggestion, you may also add the Test Environments custom field. It may be useful to have different Sub-Test Executions to test the requirement in different environments.
Quick view of Executions for Requirements from Agile Board
Creating a Sub-Test Execution from the Requirement Issue will let you track related executions on the Agile Board, so you will see all work that needs to be done to “finish” a requirement, either by developers or testers.
You can have a quick view of all test executions of a requirement, directly from the Jira Agile board, as long as the executions are created as Sub-Test Execution issues.
Test Plans as a way to consolidate test results
You may create one or more Test Plans and associate them with a given Sprint.
...