0090-laravel-testing

To write reliable Pest tests for Laravel actions, structure your test using Arrange-Act-Assert discipline, generate data with declarative factories, and isolate domain logic from HTTP cycles. This keeps tests focused, readable, and resilient to refactors.

The best way to mock dependencies in Laravel Pest tests is to mock only what you own, swap the mocked collaborators into the container using resolve() and swap(), and use behavior-focused assertions. This approach reduces test brittleness and prevents external service failures.

You can create deterministic Laravel tests without external dependencies by applying the null driver strategy. This pattern allows you to build fast, predictable tests by replacing external services with a null driver, ensuring your test outcomes remain consistent.

Arrange-Act-Assert improves Laravel feature testing by separating data setup, action execution, and outcome verification into distinct phases. This discipline enforces focused, readable tests and validates database state transitions and request/response behavior clearly.

You should use declarative factories instead of raw database inserts when you want intent-first data that does not leak database schema details. Factories keep your Pest tests maintainable and focused on the domain logic rather than underlying table structures.

Yes, you can use Pest testing patterns for both unit and feature tests in Laravel. Use feature tests for complete HTTP cycles and unit or action tests to isolate domain logic, applying container-based resolution and mocking to maintain clean separation.