Page History
...
This sheet presents a table listing requirements ("Story" issue type) impacted by defects from your exported issues.
| Column | Notes |
|---|---|
Story Key | Issue key of the Test ExecutionStory |
| Summary | Summary of the Test ExecutionStory |
| 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:
- adding/removing columns
- changing the level of detail in the columns
Exercise 1: add a field from the related Test Execution issue
Let's say we have a "Description" field on the Test Execution issue that we want to show on the report.
We can copy the column "Summary" and adapt it.
...
| Priority | Priority of the Story |
|---|---|
| Component | Component of the Story |
| Total linked defects | Count of unique defect issues linked to a given requirement story |
"DefectSummary" sheet
| Column | Notes |
|---|---|
Total defects reported | Count of unique defects associated with all the items from the source JQL. Should match the number of content rows on the "DetailedDefectList" sheet. |
| Total defects resolved | Count of unique defects in "Done" or "Resolved" status |
| Total defects unresolved | Difference between the first 2 columns |
| Total found outside of testing | Count of defects from "DetailedDefectList" sheet that have "found outside of testing" value in the Source column (see the description of logic below). |
| Total found in testing | Difference between "Total defects reported" and "Total found outside of testing" |
"DetailedDefectList" sheet
| Column | Notes |
|---|---|
Key | Issue key of the defect |
| Summary | Summary of the defect |
Workflow Status | Workflow status of the defect |
| Affected Version | Affected Version(s) of the defect |
| Fix version | Fix Version(s) of the defect |
| Priority | Priority of the defect |
| Component | Component(s) of the defect |
| Environment | Environment of the defect |
| Reporter | Reporter of the defect |
| Assignee | Assignee of the defect |
| Linked Test Execution | Key for the Test Execution(s) linked to the defect (regardless of the link type) |
| Linked Test Key and Associated Latest Test Run Status | Key for the Test(s) linked to the defect (regardless of the link type) and the latest execution run status for the Test(s) |
| Linked Requirement Story Key and Summary | Key and Summary for the Story(ies) linked to the defect (regardless of the link type) |
| Linked Requirement Epic Key and Summary | Key and Summary for the Epic(s) linked to the defect (regardless of the link type) |
| Source | The value is "found in testing" if there is at least 1 linked Test, Test Execution, or Test Plan. The value is "found outside of testing" otherwise (e.g. if a bug is created directly from the story). |
| Date Created | "Created" date in the "dd-MM-yyyy HH:mm:ss" format |
| Time to fix | Difference between "Resolved" and "Created" dates |
"Input" sheet
| Column | Notes |
|---|---|
Key | Issue key of the item from the source JQL |
| Issue Type | Issue Type of the item from the source JQL |
| Summary | Summary of the item from the source JQL |
| Priority | Priority of the item from the source JQL |
| Component | Component of the item from the source JQL |
| Status | Workflow Status of the item from the source JQL |
| Assignee | Assignee of the item from the source JQL |
Customizing the report
The common customization actions are:
- adding/removing columns
- changing the level of detail in the columns
...
As this report is column-based, if some columns are not relevant to you, you should be able to delete them. Make sure that no temporary variables are created in the cells of those columns that are used in other subsequent columns.
Exercise 2: add more details to the Test Plan column
Let's say you want to see not only the Test Plan Key, but also the Test Plan Summary, and make it a hyperlink while you are at it.
- Navigate to the "Test Plan" column
- Edit the statement from ${Test Plan} to ${link:title=${Test Plan},href=${BaseURL}/browse/${Test Plan}}
You can apply similar changes to the Defects column by editing the following statements:
- ${TestRuns[n].ExecutionDefects[d].Key} (line 6)
- ${TestRuns[n].Iterations[it].TestSteps[r].Defects[dc].Key} (line 22)
...
Keep in mind that only 1 hyperlink will be active per Excel cell (the one associated with the first line item).
You can further finetune the content and formatting via JavaScript,you can find more useful snippets in this tutorial for Xporter and DocGen as well as Xporter documentation (Cloud, DC).
Exercise 1: extend the report to custom issue types
In the "bugsormix" subtype, find all instances of
#{if (%{'${IssueTypeName}'.equals('Bug')})}
and edit them to include more than 1 type with the OR (||) syntax like this
#{if (%{'${IssueTypeName}'.equals('Bug') || '${IssueTypeName}'.equals('Defect') || '${IssueTypeName}'.equals('Incident')})}
Similar changes would allow you to account for more statuses
Keep in mind that only 1 hyperlink will be active per Excel cell (the one associated with the first line item). Also, ${Test Plan} value is treated as a single list, so if you have multiple test plans linked to the same execution and you want to separate the urls, you will need to further customize the code from the example above. On a related note, as you probably noticed, Test Plan and Test Environment are displayed slightly differently from Defects by default - comma separation, square brackets (the DocGen version has the brackets for empty Test Plan cells, doesn't have them for non-empty Test Environments).
You can further finetune the content and formatting via JavaScript,you can find more useful snippets in this tutorial for Xporter and DocGen.
Performance
Performance can be impacted by the information that is rendered and by how that information is collected/processed (especially in the "bugsormix" subtype).
...