Knowledge/Domain
Establishing that something works, and recognising when you have established nothing.
17 notes, plus everything one link away
Drag to pan · hold ⌘/ctrl and scroll — or pinch — to zoom.
Most connected first
An isolated rendered instance of a component, usable as documentation, a workbench, and a test.
Testing & Verification·15 connections
A build check that fails when coverage falls below a threshold, and what that pressure produces.
Testing & Verification·14 connections
The proportion of code executed by a test suite — a map of what is untested, not a measure of quality.
Testing & Verification·12 connections
A test that passes and fails on identical input, and the most corrosive thing a suite can contain.
Adding measurement to code so its execution can be observed, and the distortions that introduces.
The prepared data or state a test runs against.
A defect whose occurrence depends on the relative timing of concurrent operations.
Testing & Verification·11 connections
A fast, isolated test of one unit of behaviour with its collaborators replaced.
The proportion of conditional outcomes exercised — the strictest ordinary coverage metric, and the most informative.
Testing & Verification·10 connections
A real browser driven programmatically without a visible window.
Failures caused by competition for a finite shared resource rather than by any defect.
A stand-in for a real dependency during a test — and the ways a stand-in can lie.
Code no input can execute — usually a guard against a state the surrounding invariants forbid.
Comparing rendered output against a stored baseline to catch unintended visual change.
The statement in a test that must hold, and the only part that can actually fail.
Testing & Verification·9 connections
A test exercising several components together, through real interfaces rather than doubles.
Writing a failing test first, making it pass, then improving the code with the test as a net.