From 9b2c31688c56bf23f251c9cc6334b7a89699e270 Mon Sep 17 00:00:00 2001 From: dave Date: Sat, 4 Apr 2026 11:56:17 +0000 Subject: [PATCH] huskies: done 471_story_bot_command_to_show_overall_test_coverage --- ...t_command_to_show_overall_test_coverage.md | 25 +++++++++++++++++++ 1 file changed, 25 insertions(+) create mode 100644 .huskies/work/5_done/471_story_bot_command_to_show_overall_test_coverage.md diff --git a/.huskies/work/5_done/471_story_bot_command_to_show_overall_test_coverage.md b/.huskies/work/5_done/471_story_bot_command_to_show_overall_test_coverage.md new file mode 100644 index 00000000..2daa59d6 --- /dev/null +++ b/.huskies/work/5_done/471_story_bot_command_to_show_overall_test_coverage.md @@ -0,0 +1,25 @@ +--- +name: "Bot command to show overall test coverage" +--- + +# Story 471: Bot command to show overall test coverage + +## User Story + +As a user on any chat transport (Matrix, WhatsApp, Slack, or web UI), I want a `coverage` command that runs the test suite with coverage instrumentation and reports the overall coverage percentage, so I can track code quality from any interface. + +## Acceptance Criteria + +- [ ] New bot command `coverage` registered in the command registry +- [ ] Runs test coverage (e.g. cargo llvm-cov or cargo tarpaulin) and parses the overall percentage +- [ ] Reports overall line coverage percentage in chat response +- [ ] Command appears in `help` output +- [ ] Returns a clear error if the coverage tool is not installed +- [ ] Command works across all transports (Matrix, WhatsApp, Slack, web UI) via the shared command registry +- [ ] Available as both a bot command in chat and a slash command in Claude Code +- [ ] By default, reads cached coverage from .coverage_baseline for an instant response without rerunning tests +- [ ] Optional `coverage run` variant reruns script/test_coverage and reports fresh results + +## Out of Scope + +- TBD