What problem does it solve? Writing tests in Laravel projects requires consistent Pest syntax, correct assertion choices, and knowledge of Pest 4 features like browser testing and smoke testing, which developers often get wrong or skip entirely. ## Core Features & Use Cases - Pest Test Authoring: Create unit, feature, and browser tests using it()/expect() syntax, datasets, and proper mocking with Pest\Laravel helpers. - Browser & Smoke Testing: Run real-browser tests with visit/click/fill interactions and validate multiple pages for JavaScript errors in one pass. - Architecture Testing: Enforce code conventions with arch() rules such as controller suffix and inheritance checks. - Use Case: After changing a password reset flow, ask the AI 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 anime search endpoint that asserts a successful JSON response and uses a dataset for invalid query inputs.