What problem does it solve? Writing Laravel tests that are valuable, deterministic, and maintainable is hard: tests often duplicate coverage, assert implementation details instead of behavior, or depend on time, randomness, and network calls. This Skill provides a structured rule set for designing, writing, and reviewing PHPUnit-based Laravel tests so each test detects a distinct defect. ## Core Features & Use Cases - Coverage and Naming Rules: Decide what to test (decisions, failure modes, contracts), name tests as behavior specifications, and structure files to mirror the class under test. - Assertion and Endpoint Guidance: Choose subject-specific Laravel and PHPUnit assertions, cover authentication, authorization, tenant isolation, and validation for HTTP endpoints. - Isolation and Performance: Control fakes, mocks, outbound HTTP, time, randomness, and databases, plus suite-level performance settings like BCRYPT_ROUNDS and parallel runs. - Use Case: When adding a new API endpoint to a Laravel app, use this Skill to write feature tests covering auth, validation, and persisted state, then review the suite against the review checklist. ## Quick Start Ask the assistant to write or review tests for a Laravel class or endpoint using the testing-best-practices rules, for example: write feature tests for the task creation endpoint covering authentication, validation, and database state.
