Testing
Testing async Rust code with #[tokio::test] handles the basics — but complex async patterns (state machines, channels, time-dependent logic, concurrent operations) need more. This guide covers advanced async testing patterns beyond the basics. The Foundation: #[tokio::test] The baseline for async Rust tests: [dev-dependencies] tokio = { version = "1&
Testing
Rust has three places to write tests: inline in the source file, in a tests/ directory for integration tests, and in doctests. Most guides cover these in isolation. This guide covers how to organize them as your project grows — shared utilities, feature-gated tests, test fixtures, and keeping test code
Testing
Rust's error handling is excellent but undertested. Most Rust codebases test the happy path thoroughly and treat error paths as "it compiles, must be right." But error handling bugs — wrong error type returned, missing context in error messages, error chains that lose important information — cause real
Redis
Redis Pub/Sub and Redis Streams are fundamentally different messaging primitives, and each requires distinct testing approaches. Pub/Sub is ephemeral—messages are lost if no subscriber is connected. Streams are persistent—messages are stored until explicitly deleted. This guide shows how to test both reliably. Redis Pub/Sub Testing
Redis
Phil Karlton famously said there are only two hard things in computer science: cache invalidation and naming things. Testing cache invalidation is hard for different reasons—the behavior is time-dependent, state-dependent, and often involves distributed components that are difficult to simulate in isolation. This guide covers the major
Testing
Backend TDD has a straightforward feedback loop: write a test for an endpoint or function, watch it fail, implement the minimum code to pass it.
Testing
Unit tests verify logic in isolation. End-to-end tests verify user-visible behavior.
Testing
Audit logs are one of the most frequently under-tested components in production systems.