testing

Testing without mocks involves defining stage 1 evidence for your module and deciding on level 2 or 3 real dependencies to validate production behavior. This ensures tests reflect real constraints and risk rather than mocked implementation details.

Test doubles should only be used when a documented exception justifies them, such as specific constraints that prevent using real dependencies. This evidence-driven testing strategy prevents brittle tests and ensures tests demonstrate actual production behavior.

The best way to avoid brittle tests is to follow an evidence-based testing strategy that validates production behavior using real dependencies. Defaulting to mocks is avoided unless a documented exception proves doubles are necessary for specific constraints.

The five-stage testing router guides you through evidence definition to determine when mocks are appropriate versus when real dependencies should be used. It enforces documenting exception cases for test doubles, ensuring your test strategy reflects actual production risk.

Mocking limitations include creating brittle tests that validate implementation details rather than production behavior. If you rely on doubles without a documented exception, tests fail to reflect real environmental constraints and risk, reducing confidence in module correctness.