BDD in Go: What Behavior-Driven Development Actually Means

Mon, 13 Jul 2026 00:00:00 +0000

BDD — Behavior-Driven Development — is one of the most misunderstood ideas in testing. Most developers encounter it as syntax: describe, context, it. They learn the keywords, use them in a few test files, and assume they are doing BDD. But BDD is not syntax. It is a communication practice. And Go’s type system makes it possible to do BDD without the ceremony that other languages require.

This is not a tutorial on When and It — that is covered in Readable Go Tests with BDD-Style Subtests. This post is about the idea behind BDD, why most implementations of it carry unnecessary weight, and how Go’s type system maps to BDD concepts in a way that is unique among programming languages.

Why Go's testing Package Needs a Suite Layer

Sun, 05 Jul 2026 00:00:00 +0000

Go’s testing package is one of the best things about the language: no framework to install, no annotations to learn, just func Test* and go test. But past a few dozen test files, most projects hit the same wall. There is no way to group related tests, no per-test setup hook, and no way for two packages to share a database container.

That is not because the design is wrong, but because testing is deliberately minimal. It gives you a test runner and an assertion-free T type. Everything else is left to the developer: organizing tests into groups, managing setup and teardown, sharing expensive infrastructure, expressing what a test means rather than just what it does.

Philosophy on gotest

BDD in Go: What Behavior-Driven Development Actually Means

Why Go's testing Package Needs a Suite Layer