Skip to content

ci(web): enforce coverage floor in CI - #102

Merged
EmeditWeb merged 1 commit into
mainfrom
ci/web-coverage-floor
Sep 24, 2026
Merged

EmeditWeb merged 1 commit into
mainfrom
ci/web-coverage-floor

Conversation

@EmeditWeb

Copy link
Copy Markdown
Member

Summary

No linked issue — CI/tooling hardening (Phase 2 quality gates).

Adds vitest coverage thresholds and switches the CI test step to npm run test:coverage so coverage is enforced on every push and PR. The floor is set as a ratchet just below the current baseline, so it fails on regression without turning main red today.

Baseline measured locally: statements 65.62% · branches 59% · functions 70.7% · lines 66.19%.
Thresholds set: statements 60 · branches 50 · functions 65 · lines 60.

This repo is for the React web app only

  • My changes are inside src/ — N/A (config + workflow only; no src/ changes)
  • I have NOT added Rust, Soroban, or contract code
  • I have NOT added React Native or Expo-specific code
  • I have NOT hardcoded hex color values
  • All icons are from lucide-react only — N/A (no UI change)
  • No API calls made directly in page files — N/A (no page change)

Type of change

  • CI / tooling (test coverage gate)

Testing

  • npm run test:coverage exits 0 with thresholds enforced
  • npm run build passes
  • npm run lint passes
  • Test count unchanged (49 passing) — no tests removed

Mandatory before requesting review

npm run lint, npm test, and npm run build all exit 0 locally. No tests removed.

Add vitest coverage thresholds (statements 60 / branches 50 / functions 65 /
lines 60) as a ratchet just below the current baseline (65.62 / 59 / 70.7 / 66.19),
and switch the CI test step to `npm run test:coverage` so the floor is enforced
on every push and PR. Fails on regression without turning main red today.
@EmeditWeb
EmeditWeb merged commit 9c3f3e7 into main Sep 24, 2026
2 checks passed
@EmeditWeb
EmeditWeb deleted the ci/web-coverage-floor branch September 29, 2026 10:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant