Page History
...
This report lists some details of the selected Test Executions Defects 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:
- see all the Test Run Defect statuses & count for a given Test Executionversion
- see the linked Test Plans Requirements, Tests, and Defects
- track the Test Executions Defects that are taking the most time to get resolved
Output Example(s)
The following table shows template contains 4 tabs, the following tables show an example of the columns/rows you should expect.
How to use
This report can be generated from different places/contexts, including:
...
| Info | ||
|---|---|---|
| ||
| General information about all the existing places available to export from and how to perform it is available on the Exporting page. |
Source data
This report is applicable to:
In the store, you can find 2 subtypes for this template:
- "Bugsormix" - 1 or more Bug issue as well as a mix of Bug and Test Execution issues
- "Testexecs" - 1 or more 1 or more Test Execution issues
Output format
...
- Issue types having the name: "Test Execution".", "Bug"
- Bug final status being "Done" or "Resolved"
- Finished Bugs having the "Resolved date" populated
If any of these assumptions is not met, you need to update the template or the environment accordingly.
...
| Code Block | ||
|---|---|---|
| ||
project = "BOOK" and issuetype="Test Execution" order BY created DESC |
Export
...
Bugs 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 ExecutionBug" and fixVersion=1.2 order BY created DESC |
Export Test Executions and Bugs obtained
...
in a given
...
Environment
from the Issue Navigator/Search, search by Test Executions or Bugs assigned to that Test Environment (e.g., "chrome") and then use bulk export or Export->Xporter
...
| Code Block | ||
|---|---|---|
| ||
project = "BOOK" and issuetype= in ("Test Execution", Bug) and testEnvironmentsenvironment =IS chrome order BY created DESC |
Export Bug or Test Execution from its detailed view
- open the Bug/Test Execution issue and export it using this template
...
The report shows information about the Test Executions Defects in a list form as well as provides summary tables.
Layout
The report is composed of one sheet with the information on the "Test Executions".
By default, and to avoid overload/redundancy of information, only the "Test Executions" are rendered; all the other types will not be parsed.
...
4 sheets - "ReqsImpactSummary", "DefectSummary", "DetailedDefectList", and "Input". By default, all tabs are rendered. The layout is the same regardless of the template subtype used.
"ReqsImpactSummary" sheet
This sheet will present a line per each Test Executionpresents a table listing requirements ("Story" issue type) impacted by defects from your exported issues.
| Column | Notes |
|---|---|
Key | Issue key of the Test Execution |
| Summary | Summary of the Test Execution |
| Fix versions | Fix version(s) defined in the Test Execution |
| Revision | Revision defined in the Test Execution |
| Begin Date | Timestamp of when the Test Execution started, in the format "dd-MM-yyyy hh:mm:ss" |
| End Date | Timestamp of when the Test Execution ended, in the format "dd-MM-yyyy hh:mm:ss" |
| Test Environment | Test Environment(s) defined in the Test Execution |
| Test Plan | Test Plan(s) linked to the Test Execution |
| Defects | Defects linked to the Test Execution (at either the test run or the test step level) |
| Elapsed Time | Sum of elapsed time of all associated test runs in HH:MM:SS format. Please note that it will output "00:00:00" when there are no tests associated with the execution (or your executions are really fast) and " " when there are tests in progress (i.e. "Executing" or "To Do" status). |
| #Test Runs | Number of test runs that are part of the Test Execution. |
| Passed | Number of runs in the passed status. |
| Passed (%) | Percentage of runs in the passed status. |
| Failed | Number of runs in the failed status. |
| Failed (%) | Percentage of runs in the failed status. |
| Executing | Number of runs in the executing status. |
| Executing (%) | Percentage of runs in the executing status. |
| To do | Number of runs in the to do status. |
| To do (%) | Percentage of runs in the to do status. |
| Aborted | Number of runs in the aborted status. |
| Aborted (%) | Percentage of runs in the aborted status. |
"DefectSummary" sheet
"DetailedDefectList" sheet
"Input" sheet
Customizing the report
The common customization actions are:
...