What problem does it solve?
Pest testing in Laravel projects can be verbose, brittle, and hard to maintain across large test suites. This skill centralizes guidance to write, organize, and refactor Pest tests efficiently, reducing boilerplate and ensuring consistency.
Core Features & Use Cases
- Trigger Pest guidance whenever you write, edit, or refactor tests in tests/Feature, tests/Unit, or tests/Browser.
- Support Pest 4 syntax (test/it/expect), datasets, mocking, browser testing, and Livewire components.
- Ensure compatibility with common Laravel testing workflows (RefreshDatabase, arch(), and architecture tests) and provide practical examples for real-world scenarios.
- Use-case: convert existing PHPUnit tests to Pest, add datasets for parameterized tests, and implement browser tests that verify UI flows.
Quick Start
Provide Pest-compatible test examples and guidance whenever you start writing, editing, or refactoring tests in a Laravel project.