Skip to content

docs: steer pre-release gated-marker runs to the matrix ceiling (3.13) #110

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
wjduenow merged 1 commit into from
May 21, 2026
Merged

docs: steer pre-release gated-marker runs to the matrix ceiling (3.13) #110

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions .claude/rules/testing-signal.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -108,6 +108,8 @@ SF_RUN_BQ=1 GOOGLE_CLOUD_PROJECT=<billing-project> ANTHROPIC_API_KEY=sk-... pyte

For a one-shot **pre-release** measurement of how much coverage the gated paths contribute (run all gated markers under `--cov` in a single invocation), see `CONTRIBUTING.md` § "Pre-release coverage audit". A maintainer running that before each release catches coverage regressions in the gated paths that the default badge number cannot surface.

The gated markers carry **no Python-version pin** — they run on whatever interpreter `uv run` resolves, and CI runs none of them (all are deselected by `addopts`). For maintainer runs that exercise the wheel-build (`wheel_smoke`) or console-script (`cli_subprocess`) paths, target the **matrix ceiling** (currently 3.13, issue #96) via `uv run --python 3.13 pytest -m <marker> --no-cov` so packaging/entry-point behaviour is checked on the newest supported interpreter. The live-service markers (`bigquery` / `anthropic` / `e2e`) are interpreter-invariant — run them on a single version; don't multiply paid API calls across the matrix.

The `wheel_smoke` marker (issue #47) verifies wheel-build packaging without coupling it to default CI — the test shells out `python -m build --wheel` and asserts the canonical demo file set appears under `signalforge/_demo/`. See `python-build.md` § "Shipping package data".

## End-to-end gated tests (issue #10)
Expand Down
6 changes: 6 additions & 0 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,6 +39,12 @@ default marker set. Tests gated behind `bigquery`, `anthropic`, `cli_subprocess`
`.claude/rules/testing-signal.md` § "Known gap: excluded markers"), so the
real-network and packaging paths are not instrumented in the badge number.

Run this audit against the **matrix ceiling** (currently Python 3.13 — the
highest version CI exercises) by prefixing `uv run --python 3.13`, so the
gated wheel-build (`wheel_smoke`) and console-script (`cli_subprocess`) paths
are checked on the newest supported interpreter. The gated markers carry no
version pin; they run on whatever interpreter `uv run` resolves.

Before cutting a release, run both suites and combine their coverage into one
total to catch regressions in the gated paths:

Expand Down
Loading