Mutation triage test quality rule - #65
Merged
Merged
Conversation
The triage rules told agents to add a test for an unconstrained survivor but said nothing about what that test may assert. The tempting move — pinning a mutant down by asserting on incidental output — raises the score once and then constrains an implementation detail forever, which is worse than leaving the mutant alive. State the test-side companion to the existing rule against restructuring production code: a test must read as a statement about the contract, must never name a mutant, and a survivor killable only by incidental assertions is an equivalent mutant to suppress rather than a test to write. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0184eh1G3XxvjRB11cNKyMRT
The blind-spot entry named five methods that Safe Mode leaves without mutation coverage, but stopped at the diagnosis. The names read as a fixed list when they are one run's observation, and nothing told a reader what to do when editing such a method. Label the list as observed and give a durable way to recover the current one: the Safe Mode announcements are console-only and the discarded mutants are absent from the JSON report, so the surviving trace is the CompileError sites. Require test adequacy for those methods to be argued by hand in the pull request, since neither mutation score nor line coverage carries information there. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0184eh1G3XxvjRB11cNKyMRT
Minimum allowed line rate is |
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.
No description provided.