pest-testing

To write Pest PHP tests in Laravel, use the it() and expect() syntax within tests/Feature or tests/Unit directories. This Skill applies standardized patterns and activation triggers to streamline writing, refactoring, and validating your test suite.

Yes, Pest supports browser testing in Laravel applications. You can validate browser interactions and Livewire components using dedicated browser testing patterns within the tests/Browser directory, ensuring clear separation from unit and feature tests.

Pest 4 syntax fully supports datasets and mocking utilities in Laravel tests. This allows you to efficiently handle multiple data scenarios and mock dependencies during unit and feature testing without verbose boilerplate code.

The best way to organize Pest tests is maintaining a clear separation across tests/Feature, tests/Unit, and tests/Browser directories. This structure ensures that unit logic, feature integrations, and browser interactions remain distinct and manageable during refactoring.

Refactoring Laravel tests to Pest syntax involves applying standardized patterns for it() and expect() functions, along with RefreshDatabase traits. This process streamlines validation and reduces verbosity by leveraging Pest 4 syntax and arch testing support.