Behavior-Driven Testing

Start from user behavior, not code structure. Every user-reachable path must be tested—no branch left uncovered, no edge case assumed.

Core Principles

1. Behavior over Implementation - Test what users see, not how code works
2. Exhaustive Coverage - Every branch, every condition, every edge case
3. Context Awareness - Every test must define its preconditions explicitly
4. Real Environment Validation - Mocks are tools, not destinations

Workflow Overview

Testing follows three phases. Follow them in order:

Analysis → Design → Execution → Verify Coverage → Ship (or loop back)