使用Facade::shouldReceive()可精確控制門面方法的調(diào)用、參數(shù)和返回值，適用於需要細(xì)粒度模擬的場景；2. 對於Mail、Notification等常見門面，應(yīng)優(yōu)先使用Mail::fake()等內(nèi)置fake方法，更簡潔且不易出錯；3. 模擬鍊式調(diào)用時需完整描述調(diào)用鏈如Mail::to()->send()；4. 可通過partial mock僅模擬特定方法而保留其他真實行為；5. 避免在setUp()中設(shè)置僅個別測試需要的mock，防止測試間污染；6. 使用Mail::preventStrayRequests()可防止意外的郵件發(fā)送。應(yīng)根據(jù)場景選擇mock或fake，優(yōu)先使用Laravel提供的fake輔助方法以提升可讀性和穩(wěn)定性。

Mocking facades in Laravel tests is a common practice to isolate your code and avoid side effects from external services like mail, queue, or cache. Laravel provides a clean and simple way to mock facades using the Facade::shouldReceive() method, thanks to its integration with PHPUnit and Mockery.

Here's how to do it properly:

? Use shouldReceive() on the Facade

Laravel facades are static proxies to underlying services, and they can be easily mocked using shouldReceive() . This method returns a Mockery mock instance, allowing you to define expectations.

Example: Mocking the Mail facade

 use Illuminate\Support\Facades\Mail;
use Tests\TestCase;

class UserControllerTest extends TestCase
{
    public function test_sending_welcome_email()
    {
        // Arrange: Mock the Mail facade
        Mail::shouldReceive('to->send')
            ->once()
            ->with(\App\Mail\WelcomeEmail::class);

        // Act: Call the method that sends email
        $response = $this->post('/register', [
            'name' => 'John Doe',
            'email' => 'john@example.com',
            'password' => 'secret',
        ]);

        // Assert
        $response->assertRedirect();
    }
}

? Note: Because Mail::to() returns a mailable object, we chain ->to->send to mock the actual call sequence.

? Reset or Partial Mocking

Sometimes you want to mock only certain methods of a facade and keep others real. Laravel allows partial mocks using shouldReceive() while preserving other methods.

Example: Mock only put() on Storage facade

 use Illuminate\Support\Facades\Storage;

Storage::shouldReceive('put')
    ->with('avatars/1.jpg', 'file-content')
    ->andReturn(true);

// Other methods like `get()`, `exists()` will still work normally

? Prevent All Facade Calls (Optional)

If you want to ensure no unexpected facade usage happens, you can prevent all real calls:

 Mail::preventStrayRequests();

This will throw an exception if any mail is sent without being explicitly mocked.

Alternatively, use:

 Mail::fake(); // Recommended for newer Laravel versions

? Tip : Laravel also provides Fake classes (eg, Mail::fake() , Notification::fake() ) which are often easier and more readable than manual mocking.

? Mocking vs Faking

Example using Mail::fake() (preferred for mail):

 use Illuminate\Support\Facades\Mail;

Mail::fake();

// Perform action
$this->post('/register', [...]);

// Assert message was sent
Mail::assertSent(WelcomeEmail::class);

Use fake() when possible — it's simpler and less error-prone.

?? Common Pitfalls

• Forgetting chained methods : Facades like Mail::to()->send() involve intermediate objects. You must mock the full chain.
• Over-mocking : Only mock what you need. Prefer fake() for standard facades.
• Not resetting mocks : In some cases, especially in setUp() , mocks can leak between tests. Avoid setting global mocks unless necessary.

? Pro Tip: Use shouldReceive() in setUp() carefully

If you're setting up a mock in setUp() , make sure it applies to all tests — otherwise, move it into individual test methods.

 public function setUp(): void
{
    parent::setUp();
    // Only do this if ALL tests need it
    Cache::shouldReceive('get')->andReturn('cached-value');
}

In short:
Use Facade::shouldReceive() when you need fine-grained control, but lean on Laravel's ::fake() methods when available — they're simpler and less brittle.

Basically, mock facades only when necessary, and prefer Laravel's testing helpers when they exist.

以上是如何在Laravel測試中嘲笑外牆？的詳細(xì)內(nèi)容。更多資訊請關(guān)注PHP中文網(wǎng)其他相關(guān)文章！