Automated testing, explained without the jargon

This is one of those topics that looks small until it costs you something. Here is automated testing without the vocabulary that usually surrounds it.

Most development decisions are really maintenance decisions wearing a different hat. If two people in the business would answer this differently, that gap is the actual problem.

The short version

Tests are how you change things without fear. None of that requires a large budget, only a decision and someone to own it. The version that survives contact with a real deadline is the simple one.

Why people complicate it

Most of the confusion comes from tooling rather than from the idea itself. The teams that handle this well are rarely the ones with the biggest budgets.

Cover the paths that lose money if they break. The reasoning matters more than the rule, because the rule has exceptions. The failure mode is not doing it wrong, it is doing it once and assuming it stays done.

A reasonable first step

A slow test suite is a suite nobody runs. Where this goes wrong is almost never a lack of knowledge. Check it against what you would want a competitor's site to get wrong.

What this looks like day to day

The question is rarely whether something can be built, but what it costs to keep running afterwards. Three things worth confirming about automated testing before you move on:

• Someone can say what the current setup is without going to look
• Tests are how you change things without fear — and you know whether that is true here
• There is a way to tell whether the last change to this helped

None of this needs a rewrite. Most of it is a morning's work once someone decides to do it.