Page History
...
The following table shows an example of the columns/rows you should expect.
In more depth...
Key | Summary | Fix Versions | Begin Date | End Date | Test Run Status |
---|---|---|---|---|---|
EWB-705 | CC Test Plan v1.2 | 1.2 | 17-11-2023 02:30:00 | 13-11-2023 03:00:00 | Total Tests: 3 PASSED: 1 | 33% |
EWB-607 | Demo Test Plan | Total Tests: 2 PASSED: 2 | 100% | |||
... |
How to use
This report can be generated from different places/contexts, including:
...
The template has a set of assumptions that you have to make sure that your Jira/Xray environment complies with:
...
If any of these assumptions is not met, you need to update the template or the environment accordingly.
Usage examples
...
from the Issue Navigator/Search, search by the issueType (i.e., "Test Plan") from your project (e.g., "EWB") and then use bulk export
Code Block | ||
---|---|---|
| ||
project = "EWB" and issuetype="Test Plan" order BY created DESC |
...
- from the Issue Navigator/Search, search by the release (i.e., "fixVersion") of your project (e.g., "EWB") and then use bulk export
Code Block | ||
---|---|---|
| ||
project = "EWB" and issuetype= "Test Plan" and fixVersion=1.2 order BY created DESC |
...
This sheet will present a line per each Test Plan.
Column | Notes |
---|---|
Key | issue Issue key of the Test Plan |
Summary | Summary of the Test Plan |
Fix versions | The fix versions defined in the Test Plan |
Begin Date | timestamp Timestamp of when the Test Plan started, in the format "dd/MM/yyyy hh:mm:ss" |
End Date | timestamp Timestamp of when the Test Plan ended, in the format "dd/MM/yyyy hh:mm:ss" |
Test Run Status | The number of tests that are part of the Test Plan and the status of the latest test run executed for this Test Plan. You have the results divided by PASSED, FAILED, EXECUTING, TO DO, and ABORTED |
Customizing the report
...
Let's say we have a "Description" field on the Test Plan issue that we want to show it on the report.
We can copy the column "Summary" and adapt it.
- Copy the "Test Summary" column
- Insert the copied content in a column next to the “TestRunStatus”
- The Change the header of the column to be “Description”
- Change the cell content from ${Summary} to ${Description}
change - Save the template and upload it
Performance
Performance can be impacted by the information that is rendered and by how that information is collected/processed.
The number of Test Plans and Test Runs, depending on scenarios, can be considerably high, especially with CI/CD. As this report sums up quite a lot of information, please use it wisely.
...
Known limitations
- Test Run Status are is not formatted