Skip to content

Add test coverage reporting - #263

Merged
yakew7 merged 2 commits into
yakew7:mainfrom
ahmdkaml:add-coverage-reporting
Aug 16, 2026
Merged

Add test coverage reporting#263
yakew7 merged 2 commits into
yakew7:mainfrom
ahmdkaml:add-coverage-reporting

Conversation

@ahmdkaml

Copy link
Copy Markdown
Collaborator

Summary

  • Add pytest-cov to the contributor setup dependencies.
  • Add a make coverage target that reports coverage for faircode/.
  • Keep make test unchanged.
  • Keep coverage informational with no minimum threshold or CI gate.

The change is limited to the Makefile and contributor tooling; CI can verify
the new target in the repository's Python environment.

@vercel

vercel Bot commented Aug 16, 2026

Copy link
Copy Markdown
Contributor

@ahmdkaml is attempting to deploy a commit to the yashkewlani2020-gmailcom's projects Team on Vercel.

A member of the Team first needs to authorize it.

@github-actions

Copy link
Copy Markdown

@yakew7 - new PR to review.

@yakew7
yakew7 marked this pull request as ready for review August 16, 2026 15:15
@yakew7
yakew7 self-requested a review as a code owner August 16, 2026 15:15
@yakew7
yakew7 merged commit 14c6af2 into yakew7:main Aug 16, 2026
16 of 17 checks passed
yakew7 added a commit that referenced this pull request Aug 16, 2026
#263/#264/#265/#266 added make coverage (pytest --cov=faircode) and
wired it into the profiler job as an informational, non-gating step -
but the job's install line was never updated to include pytest-cov,
so the step has failed on every run since it merged. continue-on-error:
true masked it as an overall job success, so nobody noticed - verified
by simulating the exact install line in a clean venv: pytest errors
with "unrecognized arguments: --cov=faircode --cov-report=term-missing"
without the plugin installed.

Add pytest-cov to the profiler job's install line. Verified in a fresh
venv that make coverage now actually reports real numbers instead of
erroring out. Also gitignore .coverage, the local artifact make
coverage produces.
yakew7 added a commit that referenced this pull request Aug 16, 2026
Bump snapshot to cover #262 (Shreyash0712, 5 more explainers),
#263/#264 (ahmdkaml, make coverage + non-gating CI coverage report),
and #265/#266 (new contributor Circout-sudo/Yojeet, pyproject.toml
test extra - same coverage-reporting effort as ahmdkaml's PRs, both
closing #249). Adds Circout-sudo as a new Contributors entry, the
Contributor tooling & docs area row, and the git identity map (git
author "Yojeet" vs GitHub handle).
yakew7 added a commit that referenced this pull request Aug 16, 2026
Same pending version (2.0.11), not a new version bump.

ROADMAP.md: explainer count 39 -> 44, moves the three previously
"planned" healthcare explainers (race correction, Obermeyer case,
underdiagnosis bias) from planned to done since #262 shipped them
plus two more (base rate fallacy, reject inference). Traction table
and Phase 4 contributor count refreshed.

METRICS.md: stars 43, forks 22 -> 21 (real API decrease), contributors
14 -> 15 (Circout-sudo's first PR - counted from CONTRIBUTORS.md's
list since the GitHub contributors API hadn't caught up yet, same
lag pattern as the earlier forks correction), explainers 39 -> 44.
New "2026-W33 (weekend update)" narrative note. Contributors target
raised 15+ -> 20+ since the old target was just hit.

CHANGELOG.md: added entries for #262 (five new explainers), the
make coverage feature (#263-266), and three fixes - the profiler
job's silently-failing coverage step (pytest-cov never installed,
continue-on-error masked it), the stale Build Explainers CI failure
from #262 skipping make build-explainers, and llms.txt/CONTRIBUTING.md
missing the five new explainers that README.md already had.

llms.txt and CONTRIBUTING.md's explainer table: added the five new
explainers - found missing while double-checking a changelog claim
that they'd already been wired in.
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.

2 participants