Skip to content

Enable code coverage reporting for unit tests #17

@GuiBibeau

Description

@GuiBibeau

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:testingUnit, component, coverage, and E2E testingenhancementNew feature or requestfellowshipSpring 2026 fellowship project workphase:1-foundationFoundation and engineering baseline

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions