From 9e775c7cca3c5917f892940776263e853e1d08fc Mon Sep 17 00:00:00 2001 From: Dave Date: Wed, 25 Feb 2026 09:11:27 +0000 Subject: [PATCH] story-kit: create 175_story_add_rust_test_coverage_reporting_with_cargo_llvm_cov --- ..._coverage_reporting_with_cargo_llvm_cov.md | 21 +++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 .story_kit/work/1_upcoming/175_story_add_rust_test_coverage_reporting_with_cargo_llvm_cov.md diff --git a/.story_kit/work/1_upcoming/175_story_add_rust_test_coverage_reporting_with_cargo_llvm_cov.md b/.story_kit/work/1_upcoming/175_story_add_rust_test_coverage_reporting_with_cargo_llvm_cov.md new file mode 100644 index 0000000..5c6ddcf --- /dev/null +++ b/.story_kit/work/1_upcoming/175_story_add_rust_test_coverage_reporting_with_cargo_llvm_cov.md @@ -0,0 +1,21 @@ +--- +name: "Add Rust test coverage reporting with cargo-llvm-cov" +--- + +# Story 175: Add Rust test coverage reporting with cargo-llvm-cov + +## User Story + +As a project owner, I want Rust test coverage reports generated and stored in a standard location, so that agents and QA can track whether stories improve or degrade test coverage. + +## Acceptance Criteria + +- [ ] cargo-llvm-cov is installed and runnable in the project +- [ ] Running cargo nextest via llvm-cov produces coverage output in JSON and lcov formats +- [ ] Coverage reports are written to .story_kit/coverage/server.json and .story_kit/coverage/server.lcov +- [ ] STACK.md quality gates section is updated to document the coverage command +- [ ] .gitignore excludes .story_kit/coverage/ output files + +## Out of Scope + +- TBD