pest-testing

Run php artisan make:test --pest {name} where the name excludes the suite prefix, so SomeControllerTest generates tests/Feature/SomeControllerTest.php. Add --unit for unit tests, and match the existing test() or it() convention in the target directory.

Use Test Impact Analysis with ./vendor/bin/pest --parallel --tia. Tia reruns only tests affected by recent changes and replays cached results for the rest, detecting Laravel, Symfony, Livewire, and Inertia automatically.

assertSuccessful() is the preferred specific assertion over assertStatus(200), and similar specific assertions exist like assertNotFound() for 404 and assertForbidden() for 403. Specific assertions produce clearer failure messages.

Yes, Pest 5 browser tests live in tests/Browser/ and run in real browsers using visit(), click(), fill(), and assertNoJavaScriptErrors(). They support Laravel features like Event::fake(), model factories, and RefreshDatabase.

This happens when the {name} argument includes the suite prefix, such as Feature/SomeFeatureTest. Pass only the test name without the suite folder, since artisan already places the file in the correct tests directory.

Do not use it for factories, seeders, migrations, controllers, models, or other non-test PHP code. It is scoped strictly to writing, editing, and running Pest tests in Laravel projects.