What problem does it solve? Writing Laravel tests that actually catch defects is hard: tests often assert framework behavior, duplicate coverage, depend on real time or network, or pass while testing nothing. This Skill provides a structured rule set for designing, writing, and reviewing Pest tests so each test detects a distinct defect. ## Core Features & Use Cases - Test Design Rules: Nine rule files covering naming, assertions, endpoint coverage, test data, isolation, security, performance, and review checklists. - Coverage Guidance: Directs testing of authentication, authorization, tenant isolation, validation, and security boundaries like escaping and injection. - Determinism & Performance: Enforces fakes for time, sleep, HTTP, and events, plus CI settings like BCRYPT_ROUNDS and parallel execution. - Use Case: When adding a new API endpoint, use this Skill to write feature tests covering auth failures, validation errors, cross-tenant access, and the complete persisted result, then review the suite against the checklist. ## Quick Start Ask the agent to write or review Pest tests for a Laravel class or endpoint using the testing best practices rules.
