testing

Prevent flaky integration tests by replacing static sleeps with polling, isolating state per test, and enforcing determinism and async-wait practices. This testing strategy replaces unpredictable delays with reliable hermetic tests that produce consistent assertions and diagnostics.

Use the test pyramid guidance to deliberately choose unit, integration, or e2e tests based on balancing speed, coverage, and realism. Unit tests validate isolated logic, while integration and e2e layers validate Connect RPC handlers and multi-service flows created by Forge scaffolders.

The mock-at-boundaries discipline enforces mocking external edges while keeping the system under test real. This framework ensures you mock network or service boundaries to maintain hermetic test environments without sacrificing the realism of core business logic validation.

Standardize table-driven tests for Connect RPC handlers by adopting Forge's `pkg/tdd` helpers. This library-first test vocabulary provides consistent harness usage so scaffolded contract and handler tests follow uniform patterns and reduce structural drift across the codebase.

Low signal and missed regressions often occur when tests drift into slow, flaky patterns without deliberate layering. Applying a consistent testing methodology across unit, integration, and e2e layers increases signal and ensures reliable coverage without wasting CI time.

Yes, this testing methodology directly applies to multi-service flows created by Forge scaffolders and generators. It provides specific guidance for Connect RPC handler tests, contract service tests, and end-to-end flows to ensure reliable hermetic tests across generated services.