Repository navigation
ci: report test coverage from a workflow #1063
Description
Is your feature request related to a problem? Please describe.
CI reports pass or fail only. Coverage is configured (pyproject.toml [tool.coverage.*], source = ["pcapkit"], branch = true), but no workflow measures it, so nobody can see how it moves over time.
Describe the solution you'd like
A coverage job that runs the unit suite under coverage run -m pytest on one interpreter. It publishes:
- the total and per-package table in the job summary;
- the HTML report as an artifact.
Default trigger: pushes to main and workflow_dispatch. PRs are left off to avoid adding a leg to the queue #1052 is cutting. It lives in its own workflow file, so it doesn't collide with the open unit-tests.yml PRs.
Describe alternatives you've considered
Codecov or Coveralls, which give PR deltas and history but need the owner to install an app or add a token. They can be layered on later.
Additional context
Related: #1052, and the over-testing audit filed alongside this one.
Activity
JarryShaw commentedon Oct 6, 2026
Design changed by owner ruling (paraphrased): coverage is reported on PRs as well as
main, and goes into the existing unit-test runs rather than a separate workflow.Revised plan:
unit-tests.ymlleg runs its pytest command undercoverage run. No new leg; the cost is that leg's coverage overhead, to be measured.This touches
unit-tests.yml, which #1055 and #1059 also edit, so expect a rebase after whichever merges first.JarryShaw commentedon Oct 6, 2026
Follow-up ruling (paraphrased): the PR comment doesn't have to be updated in place. A new comment per run is acceptable if the sticky version adds complexity. The worker will pick the simpler of the two, and the PR will say which.
ci(coverage): report test coverage from a workflow (#1063)
ci(coverage): report test coverage from a workflow (#1063)
ci(coverage): report test coverage from a workflow (#1063) (#1064)