laravel-tdd

Laravel TDD workflows use a red-green-refactor cycle to drive feature development with PHPUnit, applying distinct unit, feature, and integration test layers for models, controllers, jobs, and policies.

The best database testing strategies for Laravel per-test isolation are RefreshDatabase, DatabaseTransactions, and DatabaseMigrations, which manage migrations and ensure clean database state for each test.

You should choose Pest for writing new tests in Laravel, or use PHPUnit if your project already standardizes on it, with both frameworks supported through practical testing examples and patterns.

Factories provide example patterns and test data generation within Laravel TDD, integrating directly with database testing strategies like RefreshDatabase and DatabaseTransactions to validate model behavior.

The Laravel TDD workflow fully supports integration testing, specifically covering jobs and policies alongside models and controllers through structured test layers and automated PHPUnit or Pest validations.

You need RefreshDatabase when you want migrations to run and reset the database entirely per test, whereas DatabaseTransactions wraps each test in a transaction rollback for faster database testing isolation.