Tdd With Pest (Laravel)
Use when
- •Implementing new behavior with regression risk.
- •Fixing bugs via reproducible failing tests.
Default workflow
- •Write a failing test for expected behavior and one edge case.
- •Implement minimal code to pass.
- •Refactor for clarity while keeping tests green.
- •Run targeted tests, then broader suite for impacted modules.
Guardrails
- •No behavior change without test evidence.
- •Prefer deterministic fixtures and isolated state.
- •Assert business outcomes instead of internals.
Progressive disclosure
- •Start with this file for execution posture and constraints.
- •Load references only for deep implementation detail or edge cases.
Output contract
- •RED/GREEN/REFACTOR summary.
- •Test files changed and command output.
- •Remaining coverage gaps.
References
- •
reference.md - •
docs/complexity-tiers.md