Repository navigation
Conversation
eXpl0it3r
force-pushed
the
test/mutation-gaps
branch
from
November 20, 2026 07:19
2f4dc66 to
fc2f075
Compare
eXpl0it3r
force-pushed
the
test/mutation-gaps
branch
from
November 20, 2026 08:06
fc2f075 to
c41ea03
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
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.
After #294 turned up a bug none of our tests noticed, I ran Stryker.NET over the core to see where else a changed line goes unnoticed. The mutation scores:
Core/Fragmentation: 87%Core/Dom: 62%Core/Paint: 72%Core/Handlers: 44%Core/Parse: 60%This PR adds 114 tests for the surviving mutants that were worth covering, grouped by area with one commit each. Where the code doesn't do what the spec says, the test is an
[Ignore("Gap, see Spec/<x>.yml")]gap test and the gap is recorded in the manifest, that's 34 of them. Production code doesn't change.On the test support side,
LayoutHarnessnow fails a test when layout reports an exception, sinceCssBox.PerformLayoutcatches them, and theFlattenand shape recording helpers moved toTestSupportinstead of being copied around.How to test this PR?
CI should succeed.