From 030cef914c6facb60bde0d787bf6333d253fc368 Mon Sep 17 00:00:00 2001 From: dave Date: Sat, 4 Apr 2026 15:11:29 +0000 Subject: [PATCH] huskies: done 474_story_per_file_test_coverage_report_with_improvement_targets --- ...overage_report_with_improvement_targets.md | 21 +++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 .huskies/work/5_done/474_story_per_file_test_coverage_report_with_improvement_targets.md diff --git a/.huskies/work/5_done/474_story_per_file_test_coverage_report_with_improvement_targets.md b/.huskies/work/5_done/474_story_per_file_test_coverage_report_with_improvement_targets.md new file mode 100644 index 00000000..26c3547d --- /dev/null +++ b/.huskies/work/5_done/474_story_per_file_test_coverage_report_with_improvement_targets.md @@ -0,0 +1,21 @@ +--- +name: "Per-file test coverage report with improvement targets" +--- + +# Story 474: Per-file test coverage report with improvement targets + +## User Story + +As a developer, I want a standardised JSON output format for test coverage so that any language's coverage tool can produce it and huskies can read it without language-specific logic. + +## Acceptance Criteria + +- [ ] Define a standard `.coverage_report.json` format: `{ "overall": float, "threshold": float, "files": [{ "path": string, "coverage": float }] }` +- [ ] Update huskies' own `script/test_coverage` to write `.coverage_report.json` in this format (Rust via `cargo llvm-cov --json`, frontend via vitest) +- [ ] `coverage` bot command reads `.coverage_report.json` and shows overall percentage plus top 5 lowest-covered files as improvement targets +- [ ] Document the `.coverage_report.json` format in `.huskies/README.md` so other projects can produce it from any language +- [ ] Huskies server has zero language-specific coverage logic — all intelligence is in the project's `script/test_coverage` + +## Out of Scope + +- TBD