Repository navigation
ci(backend): run mutation testing monthly in shards - #399
Merged
Merged
Conversation
- add `just mutation`: mutmut over app/ against one shared throwaway Postgres, listing functions whose survivor count exceeds a committed baseline - add `just mutation-baseline` to accept triaged survivors - let the test suite use an already-running Postgres (TEST_POSTGRES_HOST/PORT) and give each forked mutant run its own database - schedule the run in the Ops workflow and upload the survivor lists
- run local mutation testing at low priority on half the cores; the Ops job uses all of them - fail after 60s if the throwaway Postgres never accepts connections - document cached verdicts and full-run-only rebaselining - reuse the Postgres coordinates helper for xdist workers - relock with the pinned uv version
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
- split the Ops mutation job into six matrix shards by mutant name, so each stays well inside the job time limit - move it to its own monthly schedule; the other Ops jobs stay weekly - pass mutant globs through to mutmut without shell expansion - document rebaselining from the shards' survivor lists
simonvanlierde
changed the title
Nearly every API test passes through the middleware and runtime, so their mutants are slow and one app.core shard outran the job limit. The common shard now also catches any new app.api package.
Baseline of 4351 survivors across 583 functions, taken from all eight Ops shards. Also documents that route handlers are not mutated because mutmut skips decorated functions.
This was referenced Oct 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Runs mutmut over the backend app monthly in the Ops workflow (or on demand with
operation: mutation), split into eight shards by package so each stays inside the job time limit, and uploads each shard's survivor list. It reports functions whose survivor count is above a committed baseline and never fails on survivors. Run it locally withjust mutation, narrowed with mutant globs; it runs at low priority on half the cores.Refs #169.