comprehensive-testing

# Comprehensive Testing > Based on [Anthropic's Claude Code Best Practices](https://www.anthropic.com/engineering/claude-code-best-practices) and community patterns ## Core Philosophy > "Claude performs best when it has a clear target to iterate against—a test case provides concrete success criteria." Testing is not about proving code works; it's about **designing code that is testable** and **documenting expected behavior**. --- ## Test Pyramid ``` /\ / \ E2E Tests (10%) /----\ - Full user flows / \ - Slowest, most brittle /--------\ / \ Integration Tests (20%) /------------\ - Component interaction / \ - Real dependencies /----------------\ Unit Tests (70%) - Single function/method - Fast, isolated, many ``` | Level | Speed | Scope | When to Use | |-------|-------|-------|-------------| | Unit | <10ms | Single function | All logic | | Integration | <1s | Multiple components | APIs, DB | | E2E | <30s | Full flow | Critical paths | --- ## TDD Workflow (Anthropic Recommended) ### The 6-Step Process ``` 1. WRITE TESTS FIRST ↓ 2. VERIFY TESTS FAIL ↓ 3. COMMIT TEST SUITE ↓ 4. IMPLEMENT CODE ↓ 5. VERIFY WITH SUBAGENT ↓ 6. COMMIT IMPLEMENTATION ``` ### Step 1: Write Tests First ```markdown Be EXPLICIT about TDD to avoid mock implementations: "I want to implement [feature] using TDD. First, write tests for [expected behavior] with these input/out...