Shrink the Witness Before a Flake Freeze Can Open
An agent patch does not earn a flake freeze from one red run on a wide fixture. The freeze may open only after the property predicate, the stopped witness, and a disagreeing rerun series are all on the same record. A stable failure is a reject, and a stable pass is not a freeze. That rule is narrower than rerunning a suite until it turns green. A rerun hides a regression when the input is still…
The brief outlines a decision-making process for classifying test failures in software development. The process involves shrinking a failing test case, or "witness," by repeatedly running the test with progressively smaller inputs until the failure stops. The shrink loop stops when the next candidate input no longer fails, or when the candidate is identical to the current input.
The witness, or stopped fixture, is then used to determine the outcome of the test. The brief emphasizes the importance of maintaining a stable failure identity during the shrinking process and highlights the role of identifiers such as patch digest, property id, fixture digest, and seed in classifying test results.
Brief written by urgent.news from Dev.to's own syndicated text. Machine-written — may contain errors; check the original before relying on it.
