What problem does it solve? Writing consistent, maintainable Pest tests in a Laravel project requires remembering dozens of conventions — test file naming, describe block structure, dataset shapes, factory usage, and assertion idioms. This Skill encodes those rules so every test you write or update follows the same standard and passes a mandatory style review gate. ## Core Features & Use Cases - TDD Workflow Enforcement: Guides test-first development using the t_wada red-green-refactor cycle, including characterisation tests before refactoring uncovered code. - 15 Core Testing Rules: Covers test file naming (one file per production class), describe-per-method structure, AAA markers, beforeEach shape, feature request style, assertion patterns, datasets, and thin controller tests. - Long-Tail Checklist: A references/checklist.md file details factories, mocks, datasets, event listeners, regression tests, and contract-drift tests, enforced by a mandatory review gate on every test diff. - Use Case: When adding a feature test for a new invoice endpoint, the Skill ensures you build URLs with route(), chain assertions correctly, group cases in request-flow order, and mock delegated services rather than re-covering their logic. ## Quick Start Write a Pest feature test for the invoice store endpoint following the project's Laravel testing conventions.
