How Go Actually Tests: Data From 1,000 Repositories
We parsed 720,118 test functions across the 1,000 most-starred Go repos. What the data says about parallelism, sleeps, golden files, and containers.
gotest VS Code Extension: Suite-Aware Go Testing
The gotest VS Code extension makes Go test suites visible in your editor: discovery, run/debug at any level, spec view, coverage gutters, and watch mode.
Go Tests in GitHub Actions: The gotest CI Setup Guide
Run Go tests in GitHub Actions with the gotest action: failure-focused summaries, inline PR annotations, coverage thresholds, and the focus-prefix guard.
Contract Testing Go Interfaces with Generic Test Suites
Go interface contract testing with generics: define the contract in one test suite, instantiate it for every implementation, and catch drift as it happens.
Advanced Go Test Fixtures: Composition, Containers, Config
Go test fixture patterns at scale: composition, container-backed fixtures, per-test isolation, thread-safe state, and per-environment configuration.
Sharing Test Fixtures Across Go Packages
go test runs each package in a separate OS process. How do you share a database container across packages? gotest's SharedFixture model solves it.
Go Tests as Living Documentation: The Spec View
Tests as documentation that can't drift: gotest's spec view turns Go tests into living specification documents in terminal, markdown, and JSON.
Snapshot Testing in Go
Snapshot testing in Go without boilerplate: gotest.MatchSnapshot stores golden files, diffs on mismatch, works in parallel tests, and is read-only in CI.
Testing Async Code in Go Without time.Sleep
Go async tests without time.Sleep: Eventually and Consistently separate how long to wait from how often to check, so tests stay fast and stop flaking.
Go Test Watch Mode and Focused Tests: The Inner Loop
Go test watch mode, F_ focus prefixes, and spec output: how gotest compresses the change-test-read cycle from 30 seconds to under one.
Go Test Lifecycle: Setup, Teardown, and Execution Order
Go test setup and teardown, in order: suite hooks, fixture hooks, cleanup guarantees, and retries — the full gotest lifecycle from BeforeAll to AfterAll.
BDD in Go: What Behavior-Driven Development Actually Means
BDD in Go isn't syntax — it's communication. How Go's type system maps to behavior-driven development without describe/context/it ceremony or a DSL.
Your First Go Test Suite in 10 Minutes: A gotest Tutorial
Go test suite tutorial: from go install to a running gotest suite with lifecycle hooks, BDD structure, and readable spec output — in 10 minutes.
Why Your Go Tests Are Slow (and What to Do About It)
Most slow Go test suites aren't slow because of slow tests. Sequential execution, redundant setup, and shared state are what prevent parallelism.
Migrating from testify/suite to gotest
A practical guide to migrating Go test suites from testify/suite to gotest: before-and-after examples, automated migration, and what needs manual review.
Code Generation vs Reflection in Go Test Frameworks
Most Go test frameworks use reflection to find suites at runtime. gotest uses AST-based code generation with overlay filesystem injection instead.
Readable Go Tests with BDD-Style Subtests
Test names like TestCreateUser_WhenEmailInvalid_ReturnsError are hard to scan. BDD-style labeled subtests turn Go tests into living documentation.
Test Fixtures in Go: Patterns That Scale
Every growing Go project needs shared test infrastructure. Fixture patterns from global vars to DAG-based lifecycle management, and when to use each.
Organizing Go Tests Beyond func TestX
Why flat Go test functions, table-driven tests, and subtests each solve part of the organization problem — and what happens when you need all three at once.
Why Go’s testing Package Needs a Suite Layer
Go's testing package is deliberately minimal. Where growing projects hit its gaps, and the five principles behind gotest's suite layer.