Test-Driven Development specifically for Laravel applications using Pest PHP. Use when implementing any Laravel feature or bugfix - write the test first, watch it fail, write minimal code to pass.

Test Driven Development for Laravel Overview Write the test first. Watch it fail. Write minimal code to pass. This skill adapts TDD principles specifically for Laravel applications using Pest PHP, Laravel's testing features, and framework specific patterns. When to Use Always for Laravel: New features (controllers, models, services) Bug fixes API endpoints Database migrations and models Form validation Authorization policies Queue jobs Artisan commands Middleware Exceptions (ask your human partner): Throwaway prototypes Configuration files View only changes (no logic) The Laravel TDD Cycle RED Write Failing Test Write one minimal test showing what the Laravel feature should do. Feature Test Example: Verify RED Watch It Fail GREEN Minimal Laravel Code Write simplest Laravel code to pass the test. Verify GREEN Watch It Pass REFACTOR Clean Up Laravel Code After green only: Extract services for complex logic Create policies for authorization Add query scopes for reusability Use events for side effects Laravel Specific Test Patterns Database Testing Authorization Testing API Testing Verification Checklist [ ] Migration test passes [ ] Model relationships tested [ ] Controller actions tested [ ] Validation rules tested [ ] Authorization tested [ ] Database state verified [ ] All tests passing [ ] Used RefreshDatabase [ ] Used factories Remember

laravel-tdd