laravel-testing

Testing patterns with Pest: Arrange-Act-Assert, proper mocking, null drivers, declarative factories. Related guides: Testing should be: Every test should follow the Arrange-Act-Assert pattern: Set up all the data and dependencies needed using factories : Perform the single operation you're testing: Verify the outcomes of your action: Actions are the heart of your domain logic and should be thoroughly tested in isolation. Critical pattern: Always resolve actions from the container using resolve() so dependencies are recursively resolved. Use swap() to replace dependencies with mocked versions. Why this pattern: Critical principle: Only mock code that you control. Never mock external services directly. Use withArgs() with a closure to verify the exact instances and values being passed: If you find yourself needing to mock an external service, create an abstraction : See Services for complete implementation examples. The null driver pattern provides deterministic, fast tests without external dependencies: Benefits of null drivers: Extend the null driver for specific test scenarios: Factories create realistic, randomized test data that makes tests more robust.