Repository navigation
Move the mutation harness to Stryker 5.1.0 - #18
Merged
Merged
Conversation
5.1.0 runs in solution context: it finds SharpCorePDF.slnx, discovers the test project, and refuses a test-projects entry in stryker-config.json. The config loses the key, its default mutate glob narrows to src/**/*.cs, and the workflow and the documented commands name the solution and scope the layer with --mutate. The scoped reading of PdfDiagnoserService.cs is 38.46% (5 killed, 8 survived, 13 mutants), against 42.86% on 5.0.0; the survivor set is the same equivalents, and the one kill that moved is a mutant 5.1.0 rejects at compile time. Recorded in docs/mutation-testing.md. Also updates parity.md to twelve PDF/A files (six profiles of each document).
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.
Summary
The stale Dependabot branch (PR #8) is applied and made to work:
dotnet-strykermoves from 5.0.0 to 5.1.0.5.1.0 runs in solution context: it finds
SharpCorePDF.slnx, discovers the test project, and refuses atest-projectsentry instryker-config.json. The change:.config/dotnet-tools.json→ 5.1.0.stryker-config.json→ notest-projects; the defaultmutateglob narrows tosrc/**/*.cs.mutation.yml→--solution SharpCorePDF.slnx --mutate "src/$LAYER/**/*.cs"; one job still measures one layer..clinerules/tooling.md,README.md,docs/mutation-testing.md→ the documented commands use the solution.Evidence
PdfDiagnoserService.cs: 38.46% (5 killed, 8 survived, 13 mutants), against 42.86% on 5.0.0. The survivor set is the same equivalents the 1.7.0 record already explains (the redundant null guard, the message string, the fourConfigureAwait, the two warning merges); the one kill that moved is a mutant 5.1.0 rejects at compile time.stryker-config.jsonparses;mutation.ymlparses withyaml.safe_load.dependabot/nuget/dot-config/dotnet-stryker-5.1.0branch is deleted.Note
The solution context means a layer run builds the whole solution and then mutates only that layer's files; the weekly sweep is unchanged in what it reports, and one job still measures one layer.
Also updates
docs/parity.mdto twelve PDF/A files (six profiles of each document) after PDF/A-4.