From 0b9b5a70093859930d67a98224fe7b6e834013d8 Mon Sep 17 00:00:00 2001
From: Yojeet <84186427+Circout-sudo@users.noreply.github.com>
Date: Sun, 16 Aug 2026 17:23:08 +0200
Subject: [PATCH] Add pytest-cov coverage reporting (informational, not a CI
 gate)

Closes #249

- Add a `test` extra to pyproject.toml (pytest, pytest-cov)
- Add a `make coverage` target; `make test` output is unchanged
- CI's profiler job installs the new `test` extra and runs a new,
  separate "Coverage report (informational)" step via `make coverage`,
  right after the existing `make test` step (which is untouched)

No --cov-fail-under is set anywhere, so this can never fail a PR on a
coverage threshold - it's visibility only, as requested in the issue.

Baseline on this run: 82% overall coverage across faircode/.
Weakest spots: figures.py (0%), cli.py (51%), report.py (64%),
benchmark.py (72%) - good candidates for a follow-up issue.

README coverage badge (mentioned as optional in #249) is not included
here since it needs a live coverage service (Codecov/Coveralls) set up
by the maintainer first.
---
 .github/workflows/audits.yml | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/.github/workflows/audits.yml b/.github/workflows/audits.yml
index cc2e910..d4f5e1c 100644
--- a/.github/workflows/audits.yml
+++ b/.github/workflows/audits.yml
@@ -120,6 +120,11 @@ jobs:
 
       - name: Run profiler tests
         run: make test
+        
+      - name: Coverage report (informational)
+        # No --cov-fail-under, so this can't fail the build - just visibility
+        # into which faircode/ branches the 187 tests actually reach.
+        run: make coverage
 
       - name: Smoke-test the CLI
         run: |