Skip to content

Reconcile coverage threshold mismatch between CONTRIBUTING.md (80%) and jest.config.js (60%) #130

Description

@meshackyaro

Description

CONTRIBUTING.md's Guidelines section states "Tests required for new utilities (minimum 80% coverage)". jest.config.js's actual enforced coverageThreshold is { global: { branches: 60, functions: 60, lines: 60, statements: 60 } } — 20 points lower than what the contribution guide tells new contributors to hit, across every metric. A contributor following CONTRIBUTING.md's stated bar would be doing meaningfully more work than the CI-enforced minimum actually requires, or conversely, a PR that meets the enforced 60% (and thus passes CI) could still be seen as under-tested against the documented 80% expectation, with no build check to tell the reviewer which bar applies.

Component

SDK

Difficulty

🟢 Easy

Tasks

  • Decide which number is the real target — align jest.config.js's coverageThreshold up to 80% if genuinely wanted (checking current coverage headroom first), or lower CONTRIBUTING.md's stated figure to match the enforced 60%
  • Update whichever side is wrong so both agree

Acceptance Criteria

  • CONTRIBUTING.md and jest.config.js state the same coverage bar

Estimated Time

<1 day

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions