Advanced Go Test Fixtures: Composition, Containers, Config

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

A single fixture gets you started: start a thing, stop a thing, point your tests at it. Real projects need more. Fixtures that compose into dependency graphs, containers that survive flaky startup, per-test isolation that keeps parallel tests from stepping on each other, and configuration that adapts to each environment. These are the patterns that emerge when fixtures grow beyond a single struct with two hooks.

If you are new to gotest fixtures, Test Fixtures in Go covers the fundamentals: struct types with lifecycle hooks, automatic dependency resolution, DAG-based ordering. Sharing Test Fixtures Across Go Packages covers cross-package sharing through JSON state transfer and subprocess lifecycle management. This post assumes you have built your first fixture.

Sharing Test Fixtures Across Go Packages

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

go test compiles each package into a separate test binary and runs it as a separate OS process. That design buys you isolation, and it makes one thing structurally difficult: sharing a fixture across packages. A Postgres container that pkg/user, pkg/order, and pkg/billing all need. A Redis instance that three packages query. A schema migration that should run once for the entire test run, not once per package. Sharing any of these means crossing process boundaries.

Deep Dive on gotest

Advanced Go Test Fixtures: Composition, Containers, Config

Sharing Test Fixtures Across Go Packages