# Keep every rerun result when the failure is intermittent

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json

---

## Keep every rerun result when the failure is intermittent

ID: MHC-D-RESEARCH-0973 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/keep-every-rerun-result-when-the-failure-is-intermittent

Rerunning until green edits the story, not the software.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- An unchanged test alternates between passing and failing.

### Avoid when

- No fixed number of clean reruns proves the absence of intermittent defects. A test-environment failure may still reveal a real production risk.

### Explanation

Preserve the sequence of outcomes and the conditions of each attempt. First establish that the result varies without the intended code change. Then investigate candidate dependencies such as concurrency, test order or external services instead of treating the final pass as a repair.

### Steps

1. Record version, input, environment, attempt and outcome together.
2. Compare failing and passing attempts for a specific condition that changed.
3. Test that condition deliberately in a safe environment and retain failures in the report.

### Example

A batch test passes alone but fails after another test leaves shared state behind. An isolated green run did not cover that sequence.

### Check

The evidence contains unsuccessful attempts and distinguishes a suspected condition from a confirmed cause.

### Limits

- No fixed number of clean reruns proves the absence of intermittent defects. A test-environment failure may still reveal a real production risk.

### Evidence and sources

- supports: A flaky test can pass and fail on the same code, so one successful rerun does not establish that the underlying problem was fixed. — RS-B476D6C7D31BC624. Repeated attempts reveal variability but do not by themselves identify its cause or certify reliability. (Opening account of nondeterministic tests)
- RS-B476D6C7D31BC624: Where do our flaky tests come from? — https://testing.googleblog.com/2017/04/where-do-our-flaky-tests-come-from.html

No review details supplied.
Related (use_before): https://vedokrok.com/knowledge/shrink-the-example-until-the-same-failure-is-hard-to-hide
