-
Notifications
You must be signed in to change notification settings - Fork 0
Open
Labels
area:testingUnit, component, coverage, and E2E testingUnit, component, coverage, and E2E testingenhancementNew feature or requestNew feature or requestfellowshipSpring 2026 fellowship project workSpring 2026 fellowship project workphase:1-foundationFoundation and engineering baselineFoundation and engineering baseline
Milestone
Description
User Story
As a maintainer, I want code coverage reporting for unit tests so that the team can see where the codebase lacks confidence.
Context
Coverage should guide the team, not become a vanity metric. This issue should add lightweight, visible reporting that supports better testing habits.
Acceptance Criteria
- Vitest coverage reporting is enabled
- Coverage results are visible locally and in CI
- The repo documents how to interpret and use coverage output
- Coverage reporting is structured so thresholds can be added later
- The setup does not slow local development unnecessarily
Notes
- Avoid strict thresholds too early unless they are justified
- Focus on making gaps visible first
- Use this to encourage better tests on shared logic and risky code paths
Out of Scope
- Aggressive global coverage enforcement
- Retroactively testing the whole project in one issue
Size
Medium
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
area:testingUnit, component, coverage, and E2E testingUnit, component, coverage, and E2E testingenhancementNew feature or requestNew feature or requestfellowshipSpring 2026 fellowship project workSpring 2026 fellowship project workphase:1-foundationFoundation and engineering baselineFoundation and engineering baseline