From 2c329fa37aa37aba96bb7f2f3a01a01f4b16b917 Mon Sep 17 00:00:00 2001 From: cdeust Date: Thu, 30 Jul 2026 13:54:01 +0200 Subject: [PATCH] chore: refresh assets/badge-tests.svg from a measured count (post-#294) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit #294 (issue #293) made the tests badge the sole artifact carrying an absolute test count, checked as a monotone floor (committed <= live) so two branches adding tests never conflict on it. The version that landed in 05c7169 kept the badge at 6673 — main's pre-rebase figure carried through its own conflict resolution — which still satisfies the floor (6673 <= 6692) but is not itself a fresh measurement, only a number that happens not to overclaim. A floor that is merely non-overclaiming, left unrefreshed indefinitely, drifts further from the true count every time another PR adds tests without also regenerating this file — the badge would still say 6673 after ten more test-adding PRs, none of them individually breaking the gate. Refreshing it whenever it is touched keeps it a real answer to "how many tests," not just a number nothing yet overtook. Regenerated via `python scripts/generate_repo_badges.py --test-count 6692` (not hand-edited); 6692 is `pytest --collect-only -q` on this branch's tip (3f0522b, current main). No other file changed — the five prose/JSON docs already point at this badge rather than restating a number. Verified: `check_doc_claims.py --test-count 6692` -> "doc claims OK"; `generate_repo_badges.py --check --test-count 6692` -> "badges OK (5 checked)"; tests_py/scripts/test_generate_repo_badges.py -> 49 passed, 20 subtests passed; ruff check/format clean. --- assets/badge-tests.svg | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/assets/badge-tests.svg b/assets/badge-tests.svg index 24f33d0a..2d195655 100644 --- a/assets/badge-tests.svg +++ b/assets/badge-tests.svg @@ -1,5 +1,5 @@ - - 6673 tests passing + + 6692 tests passing