In Laravel unit testing, the logic to be tested can be isolated and side effects can be avoided by mocking dependencies. 1. Simulation dependencies can improve test speed and stability; 2. You can preset external service behavior to verify code responses; 3. Create mock objects using PHPUnit and Laravel auxiliary methods; 4. Choose mock, stub or fake according to your needs; 5. Keep the interface concise and use simulation reasonably to avoid excessive simulation.

When writing unit tests in Laravel, especially for classes that rely on external services or databases, mocking dependencies is a solid approach. It lets you isolate the logic you're testing without side effects from other parts of the system.

Why mock dependencies in unit tests?

Unit tests are meant to be fast and focused. If your class depends on something like an API client or a database connection, running real calls during tests slows things down and introduces unpredictability.

By mocking these dependencies, you simulate their behavior without actually using them. This way, you can test how your code responds under specific conditions — like a failed HTTP request or a database timeout — without having to recreate those situations in real life.

For example:

• You want to test what happens when an external service returns an error.
• You need to verify that certain methods are called with the right arguments.
• You're checking if your code handles different return values ??correctly.

Mocking gives you full control over these scenarios.

How to mock dependencies in Laravel

Laravel makes it easy to mock dependencies using PHPUnit's built-in mocking features and its own helper methods. Here's how you typically do it:

Let's say you have a class that uses a PaymentGateway contract:

 class InvoiceService {
    protected $gateway;

    public function __construct(PaymentGateway $gateway) {
        $this->gateway = $gateway;
    }

    public function chargeCustomer($amount) {
        return $this->gateway->charge($amount);
    }
}

In your test, you can mock the PaymentGateway like this:

 public function test_customer_is_charged_correctly() {
    // Create a mock instance of PaymentGateway
    $mock = $this->createMock(PaymentGateway::class);

    // Define what should happen when ->charge() is called
    $mock->method('charge')->willReturn(true);

    // Inject the mock into the class being tested
    $service = new InvoiceService($mock);

    // Run the test
    $result = $service->chargeCustomer(100);

    $this->assertTrue($result);
}

This keeps the test lightweight and predictable.

When to use mocks vs. fakes vs. stubs

It's easy to confuse different types of test doubles. Here's a quick breakdown:

• Mocks – Pre-programmed objects that set expectations about which methods should be called and with what arguments.
• Stubs – Provide predefined responses but don't care how many times they're called.
• Fakes – Simplified implementations (like an in-memory database) that behave really but aren't production-grade.

In most cases, when people talk about "mocking" in Laravel, they're referring to using mocks or stubs via PHPUnit.

If all you care about is returning a value to keep your code flowing, a simple stub is enough. But if you need to assert that a method was called exactly once with certain arguments, go with a mock.

Tips for effective dependency mocking

• Keep your interfaces clean: The easier a class is to instantiate with mocks, the better.
• Don't over-mock: Mock only what you need. Avoid mocking too many layers or internal logic.
• Use Laravel's built-in helpers: Like $this->mock() or $this->instance() for binding mocks into the container.
• Name your variables clearly: instead of $mock , use something like $paymentGatewayMock so it's obvious what you're working with.

Also, remember that not everything needs to be mocked. Sometimes integration tests with real dependencies are more valuable — just save those for a separate test suite.

Basically that's it.

The above is the detailed content of Unit testing with mocked dependencies in Laravel. For more information, please follow other related articles on the PHP Chinese website!