Standardize draft articles with YAML frontmatter including title, date, topics, related, and abstract. Expand README drafts section into a table listing all drafts with topics. Add "Testing Telos" to published articles.
1.2 KiB
1.2 KiB
| title | date | topics | related | abstract | |||
|---|---|---|---|---|---|---|---|
| On Flakiness | 2026-04-20 |
|
A flaky test is the software-testing expression of Heraclitus' river — you can never step into the same test run twice. Rather than quarantining or deleting, flakiness ought to be read as a signal that one of our background assumptions about determinism is wrong, and interrogated on those terms. |
On Flakiness — or, Heraclitus and the Non-Deterministic Test. You have direct pain here from the Appium Mac2 multi-monitor work. A flaky test is the software-testing expression of Heraclitus' river1 — you can never step into the same test run twice. But a flaky test isn't nothing; it's a signal that one of your background assumptions about determinism is wrong. The usual move is to quarantine or delete; the philosophical move is to ask what the flakiness is telling you about your model of the system. Martin Fowler's "Eradicating Non-Determinism in Tests"2 is the standard reference but deserves to be argued with rather than cited.