Database Testing
PocketBase is an open-source backend in a single Go binary: embedded SQLite database, realtime subscriptions, file storage, auth, and an extensible Go framework — all in one 30MB executable. It's become popular for indie projects, prototypes, and small teams who want a real backend without the operational overhead. Testing
Go
Go's race detector is a built-in tool that instruments your program to detect concurrent access to shared memory without synchronization. It's one of the most effective dynamic analysis tools available in any language — and it ships with the standard Go toolchain. Enabling the Race Detector Add
HTMX
Go's net/http/httptest package makes testing HTMX endpoints straightforward — create a recorder, set the HX-Request header, call your handler, and assert on the HTML response. This works with any Go web framework: Gin, Chi, Echo, or stdlib http.ServeMux. Go's speed makes HTMX integration tests
Testing
NATS JetStream persistence introduces durable consumers, sequence-based message tracking, and stream retention policies. Testing these means verifying that a consumer resumes exactly where it left off after restart, that exactly-once deduplication works, and that your stream retention policy doesn't silently discard messages your consumers haven't read
Database
Goose is the most widely-used database migration tool in the Go ecosystem, but its simplicity makes it easy to ship migrations without testing them. This guide covers a complete testing strategy using testcontainers-go, Go's standard testing package, up/down migration verification, and SQL assertion patterns that integrate naturally
Testing
gRPC-Web brings protocol buffer-based communication to browser clients, but testing it requires tools at every layer: buf for schema validation, gomock for server unit tests, grpc-web-fake for browser mocks, and Playwright fetch interception for end-to-end tests. This guide covers all of them. gRPC-Web extends gRPC to the browser by wrapping
Testing
Go's testing package has no built-in snapshot testing, but two libraries fill the gap: cupaloy (simpler, widely used) and go-snaps (more features, testify integration). Both capture test output to files, compare on future runs, and update via an environment variable flag. This guide covers both with practical examples.
Testing
NATS testing is unusually clean compared to other message brokers: you can run an embedded NATS server in the same process as your tests with zero Docker setup. This guide covers testing core pub/sub, JetStream persistent streams, and the key-value store using Go's testing package and the
Go
CLI tools are deceptively hard to test. They interact through stdin and stdout, depend on environment variables and working directories, return exit codes instead of values, and often spawn subprocesses. Most teams settle for a few manual smoke tests and call it done. When the CLI breaks in a way
Go
Go has had WebAssembly support since Go 1.11 via GOARCH=wasm GOOS=js, and since Go 1.21 via the WASI target GOOS=wasip1. Testing Go WASM code requires a different test runner than the standard go test command — either the wasm_exec.js Node.js harness for browser-targeted
Temporal
Temporal activities are where your workflow touches the outside world — HTTP calls, database writes, email sends. Testing workflows in isolation means replacing activities with mocks that return predictable values without making real external calls. Why Mock Activities Activities in Temporal are the "impure" part of the system — they
Go
Data races are one of the hardest bugs to find in concurrent programs. Go ships with a built-in race detector that catches them at runtime — no external tools, no setup, just a flag. What Is a Data Race? A data race occurs when two goroutines access the same variable concurrently,