laravel-testing

Use it() or describe() blocks with $this->get(), post(), or postJson() to make requests, then chain assertions like assertOk() or assertJsonPath(). Apply the RefreshDatabase trait via uses() in Pest.php for database isolation.

Use Http::fake() with URL patterns mapped to Http::response() stubs, and call Http::preventStrayRequests() to fail on unmocked calls. Verify requests afterward with Http::assertSent() and closure-based matchers.

Laravel 13 supports both Pest 4 and PHPUnit 12. Pest offers a concise BDD syntax with datasets and arch() tests, while PHPUnit uses class-based tests with PHP attributes like #[Test] and #[Seed]. Both run through the same php artisan test command.

Yes, use Queue::fake() and Event::fake() before triggering actions, then assert with Queue::assertPushed() and Event::assertDispatched(). Closures let you verify payload contents, and Bus::fake() covers batched and chained jobs.

Slow tests usually come from hitting a real database or running sequentially. Configure sqlite :memory: in phpunit.xml, run ./vendor/bin/pest --parallel, and use --profile to identify the slowest tests.

Call Sanctum::actingAs($user, ['abilities']) before making requests to authenticate without real tokens. For web routes, use $this->actingAs($user) with an optional guard name, and verify state with assertAuthenticated() or assertGuest().