Isolate mutation targets from the independent checker gate - #18
Merged
Merged
Conversation
…est-only-integration-v2
…est-only-integration-v2 # Conflicts: # mix.exs
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.
Problem
Mutation regressions invoke the full
mix testalias. The skip-checker environment variable does not bypass its unconditional checker command, so an unrelated JVM/bootstrap failure can turn a passing target into a false mutant kill.Fix
Give mutation baselines and targets an explicit
mix test.exunitpath which invokes the ExUnit task directly in the test environment. Ordinarymix testretains the complete ExUnit plus pure checker gate, regardless of inherited skip flags.Supporting information
An explicit task avoids making the documented gate depend on ambient environment state. The campaign still rejects failed baselines and noncompiling mutants; its existing target failure and timeout classification is otherwise unchanged. A dependency-free fixture exercises the actual campaign and project aliases with a deliberately broken checker, covering survival, assertion failure, baseline failure, and invalid compilation.