Skip to content

Add Qlty code coverage reporting to CI#2695

Closed
davehenton wants to merge 2 commits intoopenapi-ts:mainfrom
dh-sandbox:qlty-coverage-integration
Closed

Add Qlty code coverage reporting to CI#2695
davehenton wants to merge 2 commits intoopenapi-ts:mainfrom
dh-sandbox:qlty-coverage-integration

Conversation

@davehenton
Copy link

Summary

  • Add @vitest/coverage-v8 dependency for coverage data generation
  • Configure vitest coverage (v8 provider, lcov reporter) in all three packages
  • Generate combined coverage from the node 24 matrix entry in CI and upload to Qlty Cloud

Changes

  • package.json: Added @vitest/coverage-v8 dev dependency
  • packages/*/vitest.config.ts: Added coverage provider/reporter configuration
  • .github/workflows/ci.yml: Added coverage generation and Qlty upload steps (node 24 only)

Manual steps required

  1. Add QLTY_COVERAGE_TOKEN as a repository secret in GitHub (Settings → Secrets and variables → Actions)
    • Get the token from Qlty Cloud: Workspace Settings → Code Coverage

Test plan

  • Verify CI passes on all matrix entries
  • Verify coverage data is uploaded to Qlty Cloud from the node 24 job
  • Confirm coverage paths resolve correctly in Qlty dashboard

🤖 Generated with Claude Code

Configure vitest coverage with v8 provider and lcov reporter across all
three packages. Generate and upload combined coverage data from the
node 24 matrix entry in the test-node-versions CI job.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@davehenton davehenton requested a review from a team as a code owner March 18, 2026 14:06
@davehenton davehenton requested a review from gzm0 March 18, 2026 14:06
@netlify
Copy link

netlify bot commented Mar 18, 2026

👷 Deploy request for openapi-ts pending review.

Visit the deploys page to approve it

Name Link
🔨 Latest commit 6375d58

@changeset-bot
Copy link

changeset-bot bot commented Mar 18, 2026

⚠️ No Changeset found

Latest commit: 6375d58

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Instead of adding to package.json (which breaks the lockfile), install
the coverage dependency on-the-fly during the coverage generation step.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@davehenton davehenton closed this Mar 18, 2026
@davehenton davehenton deleted the qlty-coverage-integration branch March 18, 2026 19:46
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