Find out why your pytest tests are flaky: test order (with the culprit test), timezone, hash seed or real nondeterminism, each confirmed with a one-line repro.
-
Updated
Nov 2, 2026 - Python
Find out why your pytest tests are flaky: test order (with the culprit test), timezone, hash seed or real nondeterminism, each confirmed with a one-line repro.
Find the Go test that makes another test fail under go test -shuffle or in CI. Replays the failing order from a log, seed or search, bisects the tests that ran first to the culprit, confirms it, and prints a two-test reproduce command. Claude Code skill and standard-library Go CLI.
Find flaky tests, then find the test that poisons them. Runner-agnostic via JUnit XML; delta-debugging polluter search for pytest. Offline, zero dependencies.
Find the tests whose earlier execution makes a pytest test fail, by delta debugging over the test order
Detect RSpec examples that leak global state, resources, time travel, randomness, or filesystem changes.
Name the earlier test that pollutes a failing Jest/Vitest test. Deterministic, zero dependencies.
Find the pytest test(s) poisoning a flaky target via delta-debugging.
Find flaky tests in pytest, unittest and Django and explain why they fail.
To associate your repository with the test-pollution topic, visit your repo's landing page and select "manage topics."