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
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
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
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-
Temporal
Temporal activities are where your workflow touches the outside world — HTTP calls, database writes, email sends.
Go
Data races are one of the hardest bugs to find in concurrent programs.
Fuzz Testing
Go 1.18 shipped something remarkable: built-in fuzz testing integrated directly into go test.
Go
Table-driven tests are Go's idiomatic approach to testing multiple input/output combinations.
Go
testify is the most popular Go testing library. It provides three main packages: assert for fluent assertions, require for fail-fast assertions, mock for interface mocking, and suite for test organization. While the standard testing package is sufficient for simple cases, testify makes complex test suites significantly more readable. Installation
Go
Go ships with a built-in testing package that requires no third-party dependencies. The go test command finds and runs tests automatically.
Go
Unit tests verify logic in isolation. Integration tests verify that components work together: your code + database, your service + external API, your handler + middleware stack. Go's testing package supports both, and the patterns for integration testing are as idiomatic as those for unit testing. Separating Integration Tests Mark slow