crashlabs/huskies
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 26 Wiki Activity

huskies: create 474_story_per_file_test_coverage_report_with_improvement_targets

Browse Source
This commit is contained in:
dave
2026-04-04 12:26:50 +00:00
parent 3b7b0c82de
commit 97220f5321
1 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.huskies/work/1_backlog/474_story_per_file_test_coverage_report_with_improvement_targets.md
+5 -5
View File
@@ -10,11 +10,11 @@ As a developer, I want a standardised JSON output format for test coverage so th
## Acceptance Criteria ## Acceptance Criteria
- [ ] script/test_coverage saves per-file coverage data to .coverage_files.json (language-agnostic format) - [ ] Define a standard `.coverage_report.json` format: `{ "overall": float, "threshold": float, "files": [{ "path": string, "coverage": float }] }`
- [ ] Rust coverage: uses cargo llvm-cov --json to extract per-file line coverage - [ ] Update huskies' own `script/test_coverage` to write `.coverage_report.json` in this format (Rust via `cargo llvm-cov --json`, frontend via vitest)
- [ ] Frontend coverage: parses vitest coverage output for per-file data - [ ] `coverage` bot command reads `.coverage_report.json` and shows overall percentage plus top 5 lowest-covered files as improvement targets
- [ ] coverage bot command shows top N lowest-covered files when cached data is available - [ ] Document the `.coverage_report.json` format in `.huskies/README.md` so other projects can produce it from any language
- [ ] Format is extensible for other languages (Go, Python, etc.) — each entry has file path and line coverage percentage - [ ] Huskies server has zero language-specific coverage logic — all intelligence is in the project's `script/test_coverage`
## Out of Scope ## Out of Scope