pest-testing

Create tests with php artisan make:test --pest {name}, then use test() or it() functions with expect() assertions. Match the convention of existing tests in the same directory, and place files in tests/Feature or tests/Unit.

Run php artisan test --compact --filter=testName to execute a single test by name. You can also run an entire file with php artisan test --compact tests/Feature/ExampleTest.php or the full suite with php artisan test --compact.

Yes, Pest 4 includes browser testing that runs in real browsers. Tests live in tests/Browser and support clicking, filling forms, scrolling, multiple browsers and devices, dark mode, screenshots, and assertNoJavaScriptErrors() checks.

assertSuccessful() is the preferred specific assertion for HTTP 200 responses, while assertStatus(200) is the generic form. Pest conventions favor specific assertions like assertNotFound() and assertForbidden() over assertStatus(404) or assertStatus(403).

Use datasets for repetitive tests such as validation rules where the same logic runs against multiple inputs. Chain ->with([...]) onto a test to pass named or indexed data sets, avoiding duplicated test code.

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