Flaky Test

Server-side rules that stop people from pushing straight to important branches, requiring reviews, passing checks, and intact history instead.

The tool that resolves an application's modules into the files a browser downloads.

Automatically building and testing every change, so integration problems surface immediately.

The property that identical inputs produce identical outputs, and the foundation of caching and verification.

How it feels to build software with a given set of tools, codebase, and process, shaped mostly by how fast feedback arrives, how much a developer must hold in mind, and how often they can work uninterrupted.

A test that drives the whole running system the way a user would, from the interface down through every real dependency, buying the most confidence at the highest cost.

Waiting longer after each failed attempt, with a dose of randomness, so retries give a struggling system room to recover instead of hammering it.

Replacing the real clock in tests with one the test controls, so time-dependent code can be checked at midnight, across DST, or after an hour of retries without waiting.

Finding the commit that introduced a bug by binary search through history, testing the midpoint between a known-good and a known-bad version until one commit remains.

A fault that changes or disappears when someone tries to observe it.

Adding measurement to code so its execution can be observed, and the distortions that introduces.

A fixed-capacity cache that evicts whichever entry has gone untouched the longest.

The smallest self-contained program or set of steps that still shows a bug, and why making one is often the moment the bug gets understood.

The property that identical inputs may produce different outputs, and what it costs to test around.

A function whose output depends only on its input and which causes no observable effect outside itself.

A defect whose occurrence depends on the relative timing of concurrent operations.

Capturing real network responses once and replaying them in later test runs, which makes tests fast and deterministic but lets the recordings drift from the real service.

A previously working behavior that a change has broken.

Rerunning existing tests after every change to confirm that what used to work still works, how the suite grows one fixed bug at a time, and how teams keep it fast enough to run.

The smallest set of steps that reliably produces a fault, and the unit of real debugging.

Failures caused by competition for a finite shared resource rather than by any defect.

Replacing a real external service with a simulated one that speaks the same protocol over the network, so tests can run without the real dependency and can reproduce its failures on demand.

A fast, shallow check that a build isn't catastrophically broken, run before investing in a deeper test pass.

Helpers that build valid test objects from sensible defaults so each test states only the fields it cares about, and the Object Mother pattern they grew out of.

Running only the tests a change could plausibly affect, using dependency graphs, coverage maps, or learned models, so large suites stay fast without giving up their safety net.

The property that each test passes or fails on its own, regardless of which other tests run, in what order, or in parallel.

Civil time is a political layer over solar time, and its rules change often enough to be data.

A statement that holds only because its subject set is empty — a green result that measured nothing.