laravel-tdd

Test-driven development for Laravel applications using PHPUnit and Pest with 80%+ coverage (unit + feature). Choose layers based on scope: Use RefreshDatabase as the default for tests that touch the database: for databases with transaction support, it runs migrations once per test run (via a static flag) and wraps each test in a transaction; for :memory: SQLite or connections without transactions, it migrates before each test. Use DatabaseTransactions when the schema is already migrated and you only need per-test rollbacks. When using Inertia.js, assert on the component name and props with the Inertia testing helpers. Prefer assertInertia over raw JSON assertions to keep tests aligned with Inertia responses. - New features or endpoints in Laravel - Bug fixes or refactors - Testing Eloquent models, policies, jobs, and notifications - Prefer Pest for new tests unless the project already standardizes on PHPUnit - Write a failing test - Implement the minimal change to pass - Refactor while keeping tests green - Unit : pure PHP classes, value objects, services - Feature : HTTP endpoints, auth, validation, policies - Integration : database + queue + external boundaries - Use Unit tests for pure business logic and services. - Use Feature tests for HTTP, auth, validation, and response shape. - Use Integration tests when validating DB/queues/external services together.