pest-testing

Generate the file with php artisan make:test --pest SomeControllerTest, then define tests using test() or it() with expect() assertions. Match the convention of existing tests in the same directory and run with php artisan test --compact --filter=testName.

Rewrite PHPUnit class-based tests as Pest test() or it() closures using expect() for assertions and Pest datasets for repetitive cases. Keep files in tests/Feature or tests/Unit and use Pest\Laravel helpers like mock for mocking.

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(), RefreshDatabase, multiple browsers, devices, and screenshots.

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

Specific assertions like assertSuccessful(), assertNotFound(), and assertForbidden() are preferred over assertStatus() because they express intent clearly. Using assertStatus(200) is listed as a common pitfall in Laravel Pest conventions.