Unverified50% confidenceOpinionExact time
The mutant run is only a heuristic, and it degrades in predictable ways: reverting src/ may break imports, and mutant failures may originate outside the assertions under test; suites that assert on mocks or log strings often stay green even when behavior changes; flaky tests make the third state noisy; large monorepos require affected-test selection; and patches that legitimately rename or refactor tests trigger the churn counter.
1
Sources
50%
Confidence
Long-term
Relevance
10/19/2026
First Seen
Sources
Catching Weakened Tests with Three Git Worktrees
rss10/19/2026
Related Entities
Related Claims
UnverifiedA more covert failure pattern is when an agent, rather than fixing the underlying code, continuously adds or modifies tests until the entire test suite turns green.74% similarUnverifiedProper retry handling requires distinguishing retriable transient faults from logical errors that should not be repeated; otherwise, blind retrying may amplify the problem.69% similarUnverifiedStability is a property of a moment in time; when configuration, error strings, or release notes change, the harness should be re-run and declining scores treated as a signal of ground-truth drift.69% similarUnverifiedA flaky test means the same test sometimes passes and sometimes fails without any code change, with common causes including insufficient asynchronous waits, animation timing races, test data pollution, and external dependency jitter.69% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1066825API
curl https://kongchang.com/api/v1/knowledge/claims/1066825MCP
get_claim(id=1066825)