Laravel Tdd

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 → Verify RED → GREEN → Verify GREEN → REFACTOR → Repeat

RED - Write Failing Test

Write one minimal test showing what the Laravel feature should do.

Feature Test Example:

<?php

use App\Models\User;
use App\Models\Post;