learn-why-to-review-implementation-even-with-100-test-coverage

# Why Review Implementation Even with 100% Test Coverage? ## Overview This learning module helps junior developers understand why, as of today in 2026, human code review remains essential even when AI-generated code has 100% unit test coverage. Tests only verify code doesn't crash - humans must verify correctness, readability, and maintainability. ## Instructions Present the following content interactively. After each section, use `AskUserQuestion` to offer 3 options: - "Continue to next section" - "Show me an example" - "I have a question" --- ## Section 1: What 100% Test Coverage Actually Proves (and Doesn't) Explain what test coverage measures and its limitations: **What 100% test coverage proves:** - Every line of code is executed during tests - The code doesn't crash during execution **That's it.** Coverage doesn't verify correctness - test assertions could be inadequate, wrong, or missing entirely. **What 100% test coverage does NOT prove:** - The code behaves correctly (assertions could be wrong) - The code meets functional requirements (assertions could be inadequate) - The code is easy to understand and intuitive - The code will be easy to modify later - The variable and function names are clear - The solution is appropriately simple **The key insight:** Tests answer "Does it crash?" not necessarily "Does it work?" or "Is it good code?" All three questions matter. --- ## Section 2: Why Test Cases Need Review Since 100% coverage only proves code doesn...