Story 27: Coverage tracking (full-stack)
Add end-to-end coverage tracking: backend collects vitest coverage, records metrics with threshold/baseline tracking, and blocks acceptance on regression. Frontend displays coverage in gate/review panels with a "Collect Coverage" button. Includes 20 Rust tests, 17 Vitest tests, and 14 Playwright E2E tests. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
0
.story_kit/stories/upcoming/.gitkeep
Normal file
0
.story_kit/stories/upcoming/.gitkeep
Normal file
@@ -1,14 +0,0 @@
|
||||
# Story 27: Protect Tests and Coverage
|
||||
|
||||
## User Story
|
||||
As a user, I want explicit safeguards around test deletion and coverage regression, so quality guardrails cannot be weakened silently.
|
||||
|
||||
## Acceptance Criteria
|
||||
- Any deletion of test files requires explicit user approval.
|
||||
- Any change that disables or neuters a test (e.g., commenting out assertions) requires explicit user approval.
|
||||
- The workflow fails if coverage drops below the defined threshold.
|
||||
- Coverage regression is reported clearly before acceptance.
|
||||
|
||||
## Out of Scope
|
||||
- Introducing new test frameworks beyond those listed in `specs/tech/STACK.md`.
|
||||
- Large refactors solely to improve coverage.
|
||||
Reference in New Issue
Block a user