Skip to content

chore(coverage): emit lcov and json-summary reporters from vitest config - #230

Open
hivecommons-hive[bot] wants to merge 1 commit into
mainfrom
quality/test-coverage-reporters
Open

hivecommons-hive[bot] wants to merge 1 commit into
mainfrom
quality/test-coverage-reporters

Conversation

@hivecommons-hive

Copy link
Copy Markdown
Contributor

Test Improvement

The pushable half of #209. vitest.config.mjs only — no production code, no workflow change.

  • coverage.reporter: ['text', 'text-summary'] → ['text', 'text-summary', 'lcov', 'json-summary']. Every npm run test:coverage now also writes coverage/lcov.info and coverage/coverage-summary.json (both under the git-ignored coverage/, so the dist/ drift gate is unaffected). Log output is unchanged.
  • coverage.exclude: ['src/utils/context.ts']: a type-only module (export type Context = typeof github.context) with zero statements, which v8 renders as a misleading 0 | 0 | 0 | 0 row.

#209 chose CLI --coverage.reporter= overrides only because this file was held by #202 at the time; #202 has merged, so the reporters can live in config and the remaining workflow diff shrinks to the two publishing steps.

Verified on main @ c48bd6d: npx vitest run --coverage → 69 files / 1447 tests pass, thresholds hold, All files 99.83 | 98.35 | 100 | 99.82; coverage-summary.json total matches; npx eslint vitest.config.mjs clean.

Disjoint from open hold-gated PRs #217, #219, #221, #223, #225, #227, #229 — none touch vitest.config.mjs.

Related Issue

Refs #209 (needs-human: the Coverage summary step and actions/upload-artifact step in .github/workflows/test.yml still have to be added by a maintainer or an ISSUES_PRS_MERGE-tier agent — this agent's token lacks the Workflows permission; with this PR merged, the run: line in #209's replacement can stay as plain npm run test:coverage)


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

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

Add lcov and json-summary to the vitest coverage reporters so CI can
publish coverage/ as an artifact and a job summary without CLI reporter
overrides. Exclude src/utils/context.ts, a type-only module that v8
otherwise reports as an empty 0% row.

Signed-off-by: hivecommons-hive[bot] <hivecommons-hive@hive.kubestellar.io>
@hivecommons-hive
hivecommons-hive Bot requested a review from jpmcb as a code owner September 29, 2026 09:46
@hivecommons-hive hivecommons-hive Bot added the hold Indicates that a PR should not merge because someone has issued a /hold command. label Sep 29, 2026
@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

Copy link
Copy Markdown
Contributor Author

/kind cleanup


🐝 Hive Agent: quality | Instance: hosted-available-lke648397-260827-5q9t | SHA: c48bd6d

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

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. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants