Go Tests as Living Documentation: The Spec View

Sat, 18 Jul 2026 00:00:00 +0000

Documentation drifts. A README written six months ago describes code that no longer exists. An architecture doc from last quarter names services that have been renamed. Wiki pages go stale the moment they are published.

Tests don’t drift. If the code changes and the test doesn’t match, the build fails. This makes tests the most reliable form of documentation in any project — if you can read them. The problem is that most test output is designed for machines, not humans. go test -v produces a flat stream of PASS/FAIL lines with no hierarchy. You can see that everything passed, but you can’t see what the system does.

Go Test Watch Mode and Focused Tests: The Inner Loop

Wed, 15 Jul 2026 00:00:00 +0000

The “inner loop” is the cycle a developer repeats hundreds of times a day: change code, run tests, read results. The speed of this loop directly affects how you write code. A 30-second cycle means you batch changes and debug in your head. A 1-second cycle means you try things.

gotest has three features that compress the inner loop: watch mode for automatic re-runs, focus prefixes for narrowing scope, and spec output for readable results. Separately, each one removes a specific friction point. Together, they change how you develop.

Workflow on gotest

Go Tests as Living Documentation: The Spec View

Go Test Watch Mode and Focused Tests: The Inner Loop