Page History
...
This report lists some details of the selected Test Executions requirements (Stories or Epics) in Xray, enabling them to be extracted in an Excel format. With this ability to extract the report you can use it for analysis of trends and current testing status, or process this information to generate some metrics, for example, or even share it with someone else who still needs access to Jira.
Possible usage scenarios:
- get an overview of Requirements by Component and/or Priority
- track the time spent on specifying and executing tests associated with a given Requirement
- see all the Test Run statuses count for a given Test Execution
- see the linked Test Plans and Defects
- track the Test Executions that are taking the most timeRequirement
Output Example(s)
The following table shows an example of the columns/rows you should expect.
How to use
This report can be generated from different places/contexts, including:
...
This report is applicable to:
- 1 or more Test Execution Story or Epic issues
Output format
The standard output format is .XLSX so you can open it in Microsoft Excel, Google Sheets, and other tools compatible with this format. From those tools, you can generate a .CSV file.
...
- Issue types having the name: "Test ExecutionStory", "Epic".
- Direct issue links existing between requirements and tests (otherwise you get blank cells for most metrics related to the testing effort)
If any of these assumptions is not met, you need to update the template or the environment accordingly.
Usage examples
Export
...
Stories of your project
from the Issue Navigator/Search, search by the issueType (i.e., "Test ExecutionStory") from your project (e.g., "BOOK") and then use bulk export or Export->Xporter
Code Block | ||
---|---|---|
| ||
project = "BOOK" and issuetype="Test ExecutionStory" order BY created DESC |
Export
...
Epics associated with a given fix version
- from the Issue Navigator/Search, search by the release (i.e., "fixVersion") of your project (e.g., "EWB") and then use bulk export or Export->Xporter
Code Block | ||
---|---|---|
| ||
project = "BOOK" and issuetype= "Test ExecutionEpic" and fixVersion=1.2 order BY created DESC |
Export
...
Stories obtained on a given Test Environment
from the Issue Navigator/Search, search by Test Executions Stories assigned to that Test Environment (e.g., "chrome") and then use bulk export or Export->Xporter
...
Code Block | ||
---|---|---|
| ||
project = "BOOK" and issuetype= "Test ExecutionStory" and testEnvironments = chrome order BY created DESC |
Export
...
Story from its detailed view
- open the Test Execution Story issue and export it using this template
...