Flaky Test
A failure mode in which test results alternate between passing and failing under identical code, usually caused by nondeterministic factors.
Timeline (last 90 days)
Flaky tests turn red for no reason and trigger action; false passes turn green for no reason and conceal problems. The key difference between the two is that red failures trigger action while green passes conceal problems.
A 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.
All Facts (2)
Flaky tests turn red for no reason and trigger action; false passes turn green for no reason and conceal problems. The key difference between the two is that red failures trigger action while green passes conceal problems.
50%UnverifiedA 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.
50%