Question 1

How do I install Phake with Composer?

Accepted Answer

You can install Phake as a development dependency using Composer by running 'composer require --dev phake/phake'. This sets it up for use in your PHP project's testing environment.

Question 2

Phake vs PHPUnit mocking: which should I use?

Accepted Answer

Phake uses a verification-after-execution strategy, which can be more intuitive, while PHPUnit uses expectations set before execution and is deeply integrated into the PHP ecosystem. Choose Phake if you prefer a Mockito-like approach or find PHPUnit's mocking verbose, but stick with PHPUnit for seamless integration with its testing framework.

Question 3

How to stub a method to return a specific value in Phake?

Accepted Answer

In Phake, you can stub methods using the 'Phake::when()' syntax, similar to Mockito. For example, 'Phake::when($mock->method())->thenReturn(value)' sets up the stub to return the specified value during tests.

Question 4

Does Phake support mocking static methods?

Accepted Answer

Phake primarily focuses on instance method mocking, and its documentation doesn't highlight built-in support for static method mocking. You might need to use other techniques or libraries for static method dependencies in your tests.

Question 5

Can I use Phake with Laravel or Symfony projects?

Accepted Answer

Yes, Phake can be used with any PHP framework like Laravel or Symfony, as it's a general-purpose mocking framework. However, you may need to ensure compatibility with the framework's testing setup and dependency injection containers.

Question 6

How to verify that a method was called exactly once in Phake?

Accepted Answer

After executing your test code, use 'Phake::verify($mock)->method()->once()' to verify the method was called exactly once. This aligns with Phake's verification-based approach, where checks are made post-execution.

Phake

Overview

Use Cases

Not Ideal For

Pros & Cons

Pros

Related Projects

Found a gem we're missing?

Cons

Frequently Asked Questions