What problem does it solve? Writing consistent, correct tests in Laravel projects requires knowing Pest-specific syntax, conventions, and tooling. This Skill guides AI agents to generate, fix, and refactor Pest 4 tests that follow Laravel best practices, avoiding common mistakes like wrong artisan commands or weak assertions. ## Core Features & Use Cases - Test Creation & Conventions: Generate unit, feature, and browser tests with correct make:test --pest usage, matching existing project conventions for test() vs it(). - Pest 4 Capabilities: Covers datasets, mocking, browser testing (visit/click/fill), smoke testing for JavaScript errors, visual regression, test sharding, and architecture tests with arch(). - Assertion Best Practices: Enforces specific assertions like assertSuccessful() instead of assertStatus(200) and proper RefreshDatabase usage. - Use Case: After changing a controller, ask the agent to fix the broken feature tests, add dataset-driven validation tests, and run a filtered test suite to confirm everything passes. ## Quick Start Ask the agent to write a Pest feature test for your registration endpoint and run it with php artisan test --compact --filter.