laravel-tdd

Laravel test-driven development follows a red-green-refactor cycle: write a failing test, implement the minimal code to pass, then refactor while keeping tests green. This workflow applies to unit, feature, integration, database, queue, and notification testing scenarios.

Http::fake isolates external API calls during Laravel integration testing by intercepting outbound requests so you can assert response shapes without hitting real services. It pairs with Queue::fake, Mail::fake, Notification::fake, and Event::fake to isolate all side effects.

Database testing in Laravel TDD defaults to using the RefreshDatabase trait alongside Laravel factories and states. This ensures a clean schema state for each test while allowing you to generate predictable model data for feature and integration test assertions.

Yes, the Laravel TDD workflow supports writing failing tests and evolving code using either PHPUnit or Pest. Both frameworks utilize Laravel testing traits like RefreshDatabase and integrate with fakes for queues, mail, notifications, events, and HTTP requests.

Inertia response validation in Laravel feature tests checks the component name and props data structure returned by the endpoint. The TDD workflow guides you to write failing assertions for expected Inertia page properties before implementing the controller logic.