Overview
This is an extract / follow-up of story #23469 but specific to TTM context.
With the previous story we cannot actually cover the export of a proper traceability matrix, at least not in a generic fashion because we would need to select a campain to know which test exec to select when we export User Stories -> Tests -> Test Executions.
However, in the context of Tests, what we want to export and how the data are modeled is not really customizable so we can leverage this fixed structure by having an "Export traceability matrix (TTM)" export in the "Export" dropdown of a tracker.
"Export traceability matrix (TTM)" option is proposed only in projects with Test management service activated & initialized.
When this entry is selected a modal is displayed to the user that propose to select:
- the test campaign (only one) that will apply as filter of test executions:
- The report to be used for the "Tests case" tracker
- The report to be used for the "Campaign" tracker
- The report to be used for the "Test execution" tracker
- In order to be useful the "text execution" default report should have the "Result" column
Mock-up : figma prototype
When a report is selected for a given tracker that will:
- Identify the columns to be added in the generated xlsx
- Apply filters defined in report (search criteria), if any, to further limit the artifacts to be added in the matrix
Once selected an xlsx spreadsheet is generated with:
| First level reports' tracker fields | Test case reports' fields | Test Campaign reports' fields | Test Execution reports' fields |
| ... | ... | ... | ... |
Example of a generated matrix
- User story "one fine feature"
- covered_by "fine test one"
- covered_by "fine test two"
- User story "another example"
- covered_by "example test"
- User story selected tracker report has 3 fields: Id, title & category
- Test case selected tracker report has 2 fields: Id & title
- Test campaign selected tracker report has 3 fields: Id, title & environment
- Test execution selected tracker report has 4 fields: status, results, last executed by, last executed date
Disclaimer: the table bellow is limited by mardown tables:
- Tracker names (User story, Test case, Test Campaign, ...) are in a "merged cell" at the top of the column names (like in story #23469)
- There is an "autofilter" on each column
User story Id |
User story title |
User story category |
Test case id |
Test case title |
Test Campaign id |
Test Campaign title |
Test Campaign environment |
Test Execution status |
Test Execution results |
Test Execution last executed by |
Test Execution last executed date |
123 |
One fine feature |
Database |
456 |
fine test one |
789 |
Validation 1.0.1 |
Firefox - Linux |
Passed |
|
John Doe |
2021-12-23 ... |
123 |
One fine feature |
Database |
555 |
fine test two |
789 |
Validation 1.0.1 |
Firefox - Linux |
Failed |
I got this issue... |
John Doe |
2021-12-23 ... |
333 |
another example |
Front end |
777 |
example test |
789 |
Validation 1.0.1 |
Firefox - Linux |
Passed |
|
John Doe |
2021-12-23 ... |