ci: wire up backend and frontend coverage reporting#56
Merged
Conversation
Backend and frontend jobs now report to separate category series (backend/frontend) using the multi-category support from #55, closing the gap where the Playwright job never produced coverage at all. Frontend coverage comes from Istanbul-instrumented e2e runs (nyc -> lcov), gated behind VITE_COVERAGE so plain dev/test runs stay uninstrumented. Also rename the worker to demo-coveragetracker-dev in wrangler.json. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
demo-coveragetracker-dev | e5091ae | Jul 07 2026, 01:26 AM |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
backend-coveragejob now reports its coverage undercategory: backend(using the multi-category support from Support multiple named coverage categories per project #55).test-e2ejob now instruments the SvelteKit dashboard withvite-plugin-istanbul(gated behindVITE_COVERAGE, so plaindev/test:e2estay uninstrumented), converts the resulting Istanbul coverage to LCOV vianyc, and reports it undercategory: frontend. Previously this job produced no coverage data at all — it only uploaded the Playwright HTML report as an artifact.dashboard/tests/coverage-fixture.ts, an auto-fixture that dumps each e2e test'swindow.__coverage__to.nyc_output/; existing specs now importtest/expectfrom it instead of@playwright/testdirectly.wrangler.jsonfromcoverage-trackertodemo-coveragetracker-dev.Caveats worth knowing
demo.coveragetracker.dev) needs to be redeployed with Support multiple named coverage categories per project #55's category-aware ingest before this actually produces two distinct series — until then, the old ingest schema silently drops the unknowncategoryfield and the backend/frontend posts will overwrite each other on the same commit (no error, just a flapping single series).postCheckRunhardcodes that name, so PRs will show two identically-named checks with no way to tell them apart. Threadingcategoryinto the check name is a natural follow-up, not done here.Test plan
npm run typecheck(dashboard) — cleannpm test(backend, vitest-pool-workers) — 102/102 passingnpm run test:e2e:coverage(dashboard) — 7/7 Playwright tests pass, produces a real, source-mappedcoverage/lcov.info(~74% lines)wrangler deploy --dry-run— validates cleanly under the new Worker name🤖 Generated with Claude Code