Skip to content

chore(coverage): raise vitest coverage thresholds to the current floor - #202

Merged
mrbobbytables merged 1 commit into
mainfrom
quality/test-coverage-threshold-ratchet
Sep 28, 2026
Merged

mrbobbytables merged 1 commit into
mainfrom
quality/test-coverage-threshold-ratchet

Conversation

@hivecommons-hive

Copy link
Copy Markdown
Contributor

Test Improvement

Raises the coverage.thresholds in vitest.config.mjs from 85/83/91/85 to 95/93/98/95 (lines/branches/functions/statements).

Coverage on main @ 187c5e3 is 96.35% statements / 94.55% branches / 99.14% functions / 96.16% lines, so the old thresholds left ~11 points of slack and a regression of ~250 statements would pass build-test. The new values sit about one point under the current floor.

Verified: npx vitest run --coverage passes (1291 tests) with the new thresholds on this branch.

Files: vitest.config.mjs only — disjoint from the open error-path test PRs (#173–#200), which touch __tests__/**. Once those land, coverage will be ~99% and the thresholds can be ratcheted again.

Related Issue

Closes #201


Filed by quality agent (hold-gated mode). Human review required.

— hive: agent=quality backend=copilot model=claude-fable-5.1 copilot=1.0.88

Coverage on main is 96.35/94.55/99.14/96.16 (stmts/branches/funcs/lines)
while the thresholds were 85/83/91/85, leaving ~11 points of slack. Set
them to 95/93/98/95 so a regression of more than about one point fails
build-test.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Signed-off-by: hivecommons-hive[bot] <hivecommons-hive@hive.kubestellar.io>
@hivecommons-hive hivecommons-hive Bot added the hold Indicates that a PR should not merge because someone has issued a /hold command. label Sep 27, 2026
@hivecommons-hive
hivecommons-hive Bot requested a review from jpmcb as a code owner September 27, 2026 10:10
@hivecommons-hive

Copy link
Copy Markdown
Contributor Author

Important

Held for human review by the hive's ACMM level gate.

This PR was opened by the "quality" agent while Hive policy required a human checkpoint for that agent. Non-outreach agents are held at ACMM L3–L5; the outreach agent is always held because it publishes project-facing communication.

Hive will automatically remove the hold label once current policy no longer requires a level hold for "quality". If this is an outreach PR, a human must review it and remove the label.

@hivecommons-hive hivecommons-hive Bot added the hold Indicates that a PR should not merge because someone has issued a /hold command. label Sep 27, 2026
@github-actions

Copy link
Copy Markdown
Contributor

Please add a kind label with /kind failing-test or /kind cleanup.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

hold Indicates that a PR should not merge because someone has issued a /hold command. needs-kind

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[quality] vitest coverage thresholds sit ~11 points below actual coverage; the gate cannot catch regressions

1 participant