Paper 2 · Question 12

A: Rejecting all mocks is too aggressive — unit tests with mocks are still valuable for other purposes. The issue is that integration tests are missing, not that unit tests exist. The configuration should specify what is required, not ban useful testing patterns.

B: CLAUDE.md is the correct location for persistent test standards. Specifying concrete criteria (real database connections, API contract assertions) with examples of expected structure and fixtures gives Claude Code an unambiguous target. This addresses the root cause: the existing instructions were not specific enough about what 'integration tests' means in this codebase.

C: A review subagent adds complexity and is still probabilistic. Clear specifications in CLAUDE.md solve the issue at the source by telling Claude Code exactly what to generate, rather than correcting after generation.

D: Banning mocks from all test files is overly broad — mocks are appropriate in many unit tests. The requirement is specifically that integration tests with real connections must be included, not that mocks must be eliminated.