Repository navigation
chore(harness): check the mutation score in CI - #28
Merged
Merged
Conversation
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
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.
Adopts the mutation gate of the harness: the reusable workflow moves to
@v0.1.26(and thepollora/harnessconstraint to^0.1.26), and.harness.jsonrecords a mutation score floor,ratchet.msi: 93.With a recorded
msi, the Quality gates job also runspollora-qa check --mutation(Pest's--mutate --everything --covered-only). The gate only reports; the ratchet fails the job if the score drops under 93. The floor is a couple of points under the score measured when the tests were hardened (see the previous mutation pull request), because the figure moves a little from a run to the next.No code and no test of this repository changes. The line coverage floor is not touched.