Only write enough code to get a failing test

Instead of writing a whole test and then attempting to make it pass, only write enough code to get the test to fail.

This could be by starting with a failing assertion that is fixed with a hard-coded value and then iterating on the test to introduce the next failure before repeating the process.

This allows you to keep the feedback loop small and not write more code than is needed, to focus on the objective of the test, and not code yourself into a corner.

Was this useful? Sign up here and get more like this delivered straight to your inbox every day.