pest-testing

Create the test file with php artisan make:test --pest TestName, without prefixing Feature/ or Unit/ in the name. Write tests using test() or it() functions with expect() assertions, matching the convention used by existing tests in the same directory.

Run ./vendor/bin/pest --parallel --tia to use Test Impact Analysis. Tia reruns only tests affected by recent changes and replays cached results for the rest, including covered lines and branches.

Rewrite PHPUnit class-based tests using Pest's test() or it() functions with expect() assertions. Replace assertStatus(200) with specific assertions like assertSuccessful(), and use datasets for repetitive validation cases.

Yes, Pest 5 browser tests live in tests/Browser and run in real browsers. Use visit() to load pages, then chain actions like click, fill, and assertNoJavaScriptErrors, with support for Laravel features like Event::fake() and RefreshDatabase.

The mock function must be imported before use with use function Pest\Laravel\mock; at the top of the test file. Without this import, PHP cannot resolve the namespaced Pest function.

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