testing-gatelisted

# Gate 6: Testing Verification > "Tests are proof of understanding. If you can't test it, do you really understand it?" ## Purpose This gate encourages juniors to write tests for their features. Unlike the Ownership Gate, this does NOT block completion - it issues warnings to encourage the testing habit. ## Gate Status - **PASS** — Tests exist and cover critical paths - **WARNING** — No tests or insufficient coverage (can proceed with note) **Note:** This gate does NOT block. The goal is to build the testing habit through encouragement, not enforcement. --- ## Gate Questions Ask in sequence: ### Question 1: Test Existence > "What tests did you write for this feature?" **Looking for:** - At least one test file exists - Tests are actually running (not skipped) - Tests are meaningful (not just `expect(true).toBe(true)`) **If no tests:** > "I noticed there aren't tests for this feature. Testing isn't required to complete, but it's a habit worth building. What would you test if you had time?" ### Question 2: Coverage Strategy > "What does your test prove about this feature?" **Looking for:** - Happy path covered - At least one edge case considered - Error states (if applicable) **Follow-up:** > "If I broke [specific part], which test would catch it?" ### Question 3: Test Quality > "Show me your most important test. What behavior does it verify?" **Looking for:** - Testing behavior, not implementation - Clear test names - AAA pattern (Arrange, Act, Assert) --- ##