Skip to content

ci: move coverage flags into a test-ci recipe (match modern-di)#11

Merged
lesnik512 merged 1 commit into
mainfrom
ci/coverage-recipes
Jun 14, 2026
Merged

ci: move coverage flags into a test-ci recipe (match modern-di)#11
lesnik512 merged 1 commit into
mainfrom
ci/coverage-recipes

Conversation

@lesnik512

Copy link
Copy Markdown
Member

What

Aligns this repo's test/coverage setup with the core modern-di repo.

Before: coverage flags lived in pytest addopts (--cov=. --cov-report term-missing --cov-fail-under=100), so every pytest run — including a targeted just test path -k name — tripped the 100% gate.

After (matches modern-di):

  • addopts = "" — no implicit coverage on every run.
  • New test-ci recipe carries the coverage flags + --cov-fail-under=100; CI runs just test-ci.
  • test-branch made explicit (--cov=. --cov-branch --cov-fail-under=100).
  • just test [args] stays a plain, fast, gate-free runner.

The 100% coverage gate is still enforced in CI (verified locally: just test-ci passes at 100%); only targeted local runs stop tripping it.

🤖 Generated with Claude Code

Coverage flags lived in pytest addopts, so every pytest run — including a
targeted `just test path -k name` — tripped --cov-fail-under=100. Mirror the
core modern-di repo: empty addopts, a dedicated `test-ci` recipe carrying the
coverage flags, an explicit `test-branch`, and CI runs `just test-ci`. The
100%% gate is still enforced in CI; targeted local runs no longer trip it.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@lesnik512 lesnik512 merged commit 820b515 into main Jun 14, 2026
6 checks passed
@lesnik512 lesnik512 deleted the ci/coverage-recipes branch June 14, 2026 08:35
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.

1 participant