Repository navigation
Fix/mojo resolves unpublished shim - #9
Merged
Merged
Conversation
…atalog entries; scope per-class state; stop no-op window mutants
…king a 100% mutation score (KILLED), and pipes the full Surefire exception trace straight into the failure details. mutator-core: Catches plan-binding and resolution crashes via StructuralInvalidation when a mutation breaks downstream columns, reclassifying them as SKIPPED instead of blowing up the gate. shims (3.5 / 4.2): Drops TRUNCATE_WINDOW_FRAME on ranking functions and unordered RangeFrames—they're guaranteed no-ops that were cluttering reports with false SURVIVED results. mutator-junit5: Resets catalogs and sinks per class baseline so multi-class test runs stop bleeding mutant state and verdicts into each other. shims (3.5 / 4.2): Canonicalizes site fingerprints against pruning and minor type quirks (100L vs 100), using exprSigSet to correctly track reshaped nodes while rejecting lookalikes; re-pins goldens. mutator-junit5: Makes the AQE parity check actually test something real instead of passing vacuously against a write-once sink.
… parent POM, no reactor classes) to exercise published artifacts the exact way a real consumer pulls them from Maven Central. Test complexity ramps from a simple single-column filter all the way to a nested-schema, multi-stage pipeline. ci.yml: Adds a consumer-verification job that installs the reactor into a fresh local repository and runs the standalone project strictly against those artifacts (covering both the in-process test path and the fork-per-mutant plugin path). Regular in-repo tests run against the reactor directly, meaning they cannot catch partial publishes, missing coordinates, or parent-POM leaks. release.yml: Expands the post-publish smoke test to resolve the full consumer-facing coordinate set via scripts/verify-release.sh. During the 1.0.0 release, only a subset of modules was actually published, but the old two-artifact spot check stayed green while real-world consumer builds broke. scripts/verify-release.sh: Introduces a parameterized coordinate check against Maven Central (or --repo <id::url>) that exits with status 1 and lists any missing artifacts.
Add spark.mutator.notAppliedExemptMutators; exempt families leave both ratio terms, empty = global. Add a classification-stability guard test; disable the ratio gate in the consumer example.
wpunit13
force-pushed
the
fix/mojo-resolves-unpublished-shim
branch
from
September 25, 2026 05:20
8909ffc to
0f29096
Compare
…minated PROJECT sites (73→31 not-applied)
…ed-sig viability; WindowTest fixture observes frame truncation
…-sig check (fixes CI)
…e key (fixes stress-test cross-branch misattribution); scala 2.12 compat
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.
No description provided.