What problem does it solve? Writing consistent, idiomatic Pest tests in Laravel projects is error-prone: developers misuse artisan generators, pick weak assertions, forget dataset patterns, or skip browser-level checks. This Skill provides the conventions and syntax needed to write, fix, and refactor Pest 4 tests correctly. ## Core Features & Use Cases - Test Authoring Conventions: Correct make:test --pest usage, test()/it() matching project style, and proper placement in tests/Feature, tests/Unit, and tests/Browser. - Pest 4 Feature Coverage: Datasets, mocking via Pest\Laravel\mock, specific response assertions, browser testing with visit/click/fill, smoke testing for JavaScript errors, visual regression, sharding, and architecture tests with arch(). - Use Case: After a code change breaks your suite, ask the AI to fix the failing tests — it will run filtered tests with --compact --filter, apply specific assertions like assertSuccessful() instead of assertStatus(200), and add datasets for repetitive validation cases. ## Quick Start Write a Pest feature test for the registration endpoint and run it with a filtered artisan test command.