Repository navigation
ci: run mutation tests with Infection - #63
Merged
Merged
Conversation
The commands skip config generation when the working directory already has a .rr.yaml. Under Infection a mutant wrote one into the project root, which then failed the config tests of every later run. Assisted-By: Claude Opus 5.5
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 13 minutes. View limit detailsLimit details: You’ve used the included review currently available. Review configuration: ⚙️ Run configuration
📒 Files selected for processing (6)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Infection is installed in the workflow rather than from the phar: the Testo adapter bundled in the 0.35.6 phar writes a bootstrap that calls the unscoped `\Infection\StreamWrapper\IncludeInterceptor`, while the phar only ships `Infected\...`, so every mutant errors. It stays out of require-dev because it needs PHP 8.3+. Local run (Windows): 568 mutants, covered MSI 65%; CI (Linux): 569 mutants, covered MSI 63%, so both thresholds are 60. Assisted-By: Claude Opus 5.5
roxblnfk
force-pushed
the
ci/mutation-testing
branch
from
October 9, 2026 20:41
23e9f9f to
9f5abf8
Compare
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.
What was changed
2.x, with reports sent to the Stryker dashboard. The README gets a mutation score badge.--min-msi=60 --min-covered-msi=60.get-binaryandmake-configtests now run in their own temporary working directory. Both commands skip config generation when the working directory already contains a.rr.yaml. A mutant wrote one into the project root, and the config tests of every later run then failed.Why?
To measure test quality beyond line coverage. Most of the surviving mutants are in console output formatting and the GitHub token header, which the tests do not inspect.
Review notes
\Infection\StreamWrapper\IncludeInterceptor, so every mutant errors and is wrongly counted as killed. It stays out ofrequire-devbecause it needs PHP 8.3+.Checklist