Question 1

How do I mock static methods with Mockery?

Accepted Answer

Mockery does not natively support mocking static methods; you may need to use partial mocks or other workarounds. Check the documentation for advanced techniques, but this is a known limitation compared to some frameworks.

Question 2

Mockery vs PHPUnit mocks: which is better?

Accepted Answer

Mockery offers a more expressive DSL and features like spies, making it ideal for complex mocking needs. PHPUnit's built-in mocks are sufficient for basics and avoid extra dependencies, so choose based on your project's complexity.

Question 3

How to verify a method was called with specific arguments in Mockery?

Accepted Answer

Use expects() with with() clauses for exact parameter matching, or for spies, use shouldHaveReceived(). The README shows examples like $double->expects()->add($book) to verify calls during tests.

Question 4

Can I use Mockery with Laravel's testing framework?

Accepted Answer

Yes, Mockery integrates well with Laravel and is commonly used to mock Eloquent models or services. Its flexibility complements Laravel's container, though you may need to adjust setup for dependency injection.

Question 5

What's the difference between allows and shouldReceive in Mockery?

Accepted Answer

allows() sets up stubs where calls are optional, while shouldReceive() sets expectations where calls must occur. Both are part of the API, with allows() being a newer, more readable alternative introduced in v1.

Question 6

How to mock traits with Mockery?

Accepted Answer

Use Mockery::mock(TraitName::class) to create an object that uses the trait; Mockery automatically generates implementations for abstract methods, allowing you to stub or expect calls as needed, as explained in the Utilities section.

Mockery

What is Mockery?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions