Why Your Go Tests Are Slow (and What to Do About It)

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

go test ./... takes 90 seconds. You’ve profiled the hot tests and they’re fast. The database setup is cached. The assertions are trivial. So where does the time go?

Usually the answer isn’t slow tests. It’s slow structure: the way tests are organized determines how much work runs sequentially, how much setup gets repeated, and how much parallelism the runtime can actually use. This post looks at the three structural patterns that make Go test suites slow, and what to do about each one. The payoff is real: the benchmark later in the post takes the same example suite from 6 seconds to 0.5 seconds through structural changes alone, without touching a single test.

Performance on gotest

Why Your Go Tests Are Slow (and What to Do About It)