Question 1

What is the Pest PHP testing framework, and why has it become a preferred option for modern Laravel tests over PHPUnit?

Accepted Answer

Pest is a clean framework built on PHPUnit that offers concise functional syntax (Expectation API) and intuitive error output while remaining fully compatible with PHPUnit features and tests.

Question 2

How do you write integrated Laravel Feature tests for API endpoints and validate JSON responses?

Accepted Answer

Use methods such as $this->getJson() or postJson(), and check results with assertions such as assertStatus(200), assertJsonPath(), and assertJsonValidationErrors().

Question 3

How do the RefreshDatabase Trait and DatabaseTransactions differ in Laravel tests?

Accepted Answer

RefreshDatabase runs migrations once and isolates each test in a transaction that is rolled back at the end, while DatabaseTransactions wraps only the test in a transaction and requires an already prepared database.

Question 4

How do Model Factories and Faker simplify preparing test data?

Accepted Answer

They create fake, consistent model records that match the database through User::factory()->create(), with options to override fields and generate preset States.

Question 5

How do you replace services and Facades with Mocks in Laravel tests without breaking the system?

Accepted Answer

Use built-in fakes such as Event::fake(), Queue::fake(), or Mail::fake(), and verify sends with Mail::assertSent().

Question 6

How do you control and freeze system time in Laravel tests that depend on timeouts?

Accepted Answer

Use built-in time travel methods such as $this->travel(5)->days() or $this->freezeTime() to test expiration precisely.

Question 7

How do multi-channel Notifications work in Laravel, and how do you test them with Notification::fake()?

Accepted Answer

They send a unified notification through multiple channels (mail, database, sms, broadcast) selected by via(), and can be tested with Notification::fake().

Question 8

How do you test Jobs, Events, and mail in Laravel with fakes (Queue::fake, Event::fake, and Mail::fake)?

Accepted Answer

Fakes replace real execution with a recorder, letting you verify after the code runs that the job, event, or message was dispatched with the right data without actually running it.

Question 9

How do you test authentication and authorization (actingAs, Gates, and Policies) in Laravel applications?

Accepted Answer

Simulate the current user with actingAs and check response codes (401 for a guest, 403 for an unauthorized user, 200 for the owner); test Policies directly with Gate::forUser or $user->can.

Question 10

How do you test code that calls external APIs with Http::fake() and prevent real requests?

Accepted Answer

Http::fake intercepts HTTP client calls and returns predefined responses by pattern; Http::preventStrayRequests() blocks any unmocked request from reaching the real network.