Testing
FluentAssertions is a .NET assertion library that replaces cryptic Assert.AreEqual() calls with readable, chainable English-like syntax — making test failures self-explanatory and test code easier to maintain. Key Takeaways * FluentAssertions replaces Assert.* with a fluent .Should().Be() chain that reads like a sentence * Failure messages are dramatically more informative than
Testing
Bogus is a .NET fake data generator that creates realistic-looking test data — names, emails, addresses, phone numbers, Lorem Ipsum text — with a fluent API, making it easy to build repeatable, locale-aware test fixtures. Key Takeaways * Faker with RuleFor() creates a typed data factory that generates consistent, realistic objects * Seed the
Testing
NSubstitute is a .NET mocking library designed to be simple and readable — you set up substitutes with natural syntax instead of verbose lambda chains, making test code easier to write and review. Key Takeaways * Substitute.For() creates a mock of any interface or virtual class with no configuration needed * Returns(
Testing
BenchmarkDotNet is the standard .NET library for micro-benchmarking — it handles JIT warmup, statistical analysis, and memory allocation measurement automatically, giving you reliable, comparable performance numbers instead of naive Stopwatch timing. Key Takeaways * The [Benchmark] attribute marks methods to measure; BenchmarkRunner.Run() executes the full benchmark suite * [MemoryDiagnoser] adds allocation columns
Testing
cargo-nextest runs Rust tests faster and with better output than cargo test. Beyond the basics, it has a configuration system that lets you filter which tests run, partition tests across parallel CI jobs, retry flaky tests automatically, and produce JUnit XML for CI dashboards — all without changing test code. Key
Testing
insta captures the output of your code as a snapshot file. On future runs, it compares actual output against the saved snapshot and fails if they differ. When output changes intentionally, you review and approve the new snapshot with cargo insta review. It's the right tool when manually
Testing
wiremock-rs runs a real HTTP server in your test process. Your code under test makes actual HTTP calls — the mock server intercepts them, matches against your rules, and returns the responses you specify. No code changes required, no faking the HTTP client layer. Key Takeaways * MockServer starts a real HTTP
Testing
axum-test is a test client for Axum that sends requests directly to your router in-process — no network, no port binding, no flakiness. It gives you a clean API for building requests, asserting on responses, and managing session state across test calls. Key Takeaways * axum-test sends requests in-process — fast and port-free
Testing
tokio-test gives you utilities for testing async Rust code in isolation — mocking I/O streams, controlling time, and asserting on async behavior without requiring a real network or file system. It's the right tool when you want fast, deterministic tests for code that depends on Tokio primitives. Key
Test Automation
Replaying production traffic is conceptually simple: capture requests, store them, send them again to a different target. In practice, it is full of hard problems — authentication tokens expire, session state is tied to specific users, database operations are not idempotent, and request timing and ordering matters. This post covers the
Test Automation
Concurrent systems fail in ways that test suites almost never catch. A race condition that corrupts data might require a specific interleaving of 12 operations across 4 threads — a sequence that a random test might hit once in a billion runs, but that a model checker can find in seconds
Test Automation
Distributed systems fail in ways that are nearly impossible to reproduce with conventional tests. Race conditions, partial failures, network partitions, and subtle ordering bugs hide in the gaps between nodes, surfacing only under specific interleavings that happen to occur in production at 3 AM. TLA+ is a formal specification language