laravel-tdd

Topics in the source

• Laravel Testing with TDD
• When to Activate
• TDD Workflow for Laravel
• Red-Green-Refactor Cycle
• Setup
• PHPUnit Configuration
• Base TestCase Setup
• Model Factories

Test-driven development for Laravel applications using PHPUnit, Pest, Laravel factories, and testing helpers. Writing new Laravel applications or features Implementing API endpoints with Sanctum or Passport authentication Testing Eloquent models, relationships, scopes, and accessors Setting up testing infrastructure for Laravel projects Writing feature tests for HTTP controllers and form requests Mocking external services (queues, mail, notifications, HTTP) | Component | Target | |-----------|--------| | Models | 95%+ | | Actions/Services | 90%+ | | Form Requests | 90%+ | | Controllers | 85%+ | | Policies | 95%+ | | Overall | 80%+ | Use factories over manual create() calls One logical assertion per test Descriptive names: testguestscannotcreateproducts Test edge cases and authorization boundaries Mock external services with Http::fake(), Mail::fake() Use RefreshDatabase for clean state Don't test Laravel internals (trust the framework) Don't make tests dependent on each other Don't over-mock — mock only service boundaries Don't test private methods — test through the public interface Don't couple tests to HTML structure | Pattern | Usage | |---------|-------| | RefreshDatabase | Re

This is an excerpt. Refer to the complete source and its current requirements.