What problem does it solve? Writing consistent, modern PHP tests in Laravel projects requires knowing Pest 4 syntax, conventions, and features like datasets, browser testing, and architecture rules, which developers often get wrong or mix with legacy PHPUnit patterns. ## Core Features & Use Cases - Pest Test Authoring: Create unit, feature, and browser tests using it()/expect() syntax, datasets, and Pest-specific mocking with proper conventions. - Browser & Smoke Testing: Run real-browser tests with visit/click/fill interactions, JavaScript error checks, and multi-page smoke tests. - Architecture Testing: Enforce code conventions with arch() rules such as controller suffix and inheritance constraints. - Use Case: After changing a password reset flow, ask the assistant to write a Pest browser test that visits the sign-in page, submits the reset form, and asserts the notification was sent. ## Quick Start Write a Pest feature test for the password reset flow and run it with php artisan test --compact --filter.