What problem does it solve? Writing reliable Laravel tests requires choosing the right test layer, database strategy, and framework, and developers often struggle with inconsistent coverage, slow database tests, and untested side effects like jobs, mail, and notifications. ## Core Features & Use Cases - Red-Green-Refactor Workflow: Enforces a disciplined TDD cycle with unit, feature, and integration test layers for models, endpoints, policies, and jobs. - Database Testing Strategies: Selects between RefreshDatabase, DatabaseTransactions, and DatabaseMigrations, with in-memory SQLite configuration for fast test runs. - Fakes and Isolation: Uses Bus, Queue, Mail, Notification, Event, and Http fakes plus Sanctum auth helpers to test side effects without external services. - Use Case: When adding a new API endpoint, write a failing Pest feature test with factories and RefreshDatabase, implement the minimal controller logic, then assert the JSON structure and database state while faking queued notifications. ## Quick Start Write a failing Pest feature test for my new Laravel endpoint using factories and RefreshDatabase, then guide me through making it pass.
