action #179212
opencoordination #177042: [saga][epic] Future ideas for higher quality os-autoinst+openQA product
coordination #177045: [epic] Improved development environment for os-autoinst
[spike][timeboxed:10h] Code coverage: Create Proof of Concept report about which code is covered by which unit test
0%
Description
Motivation¶
See #176595
We want to see if such a report would look useful. For that we only need to take the generated JSON data from https://github.com/os-autoinst/os-autoinst/pull/2644 and create a proof of concept HTML page.
If it looks useful, we can work on the other ticket to generate it regularly in CI.
Acceptance Criteria¶
- AC1: Proof of Concept HTML report exists showing which line of code is covered by which .t files
Suggestions¶
- JSON Data can be retrieved from here: https://github.com/perlpunk/os-autoinst/actions/runs/13619564612 (or simply run the PR on your fork and look into your fork's Action tab)
For every source file we would have a table. Rows are the source lines, and then there would be columns for each .t file that covers a line.
e.g.
| t/foo.t | t/api/bar.t | |
|---|---|---|
| if ($x == 23) { | X | X |
| do_something(); | X |
Updated by tinita about 1 month ago
- Copied from action #176595: [retro] Code coverage: Create report about which code is covered by which unit test added
Updated by okurz about 1 month ago
- Subject changed from [spike] [10h] Code coverage: Create Proof of Concept report about which code is covered by which unit test to [spike][timeboxed:10h] Code coverage: Create Proof of Concept report about which code is covered by which unit test
Updated by okurz about 1 month ago
- Target version changed from Tools - Next to future
Updated by tinita 18 days ago
I created this: https://w3.nue.suse.com/~timueller/cbt/os-autoinst/
There can still be improvements (scrollable right side of the table), but maybe we can decide now if this looks useful in general.