I want to call my mocked method twice with different expected arguments. This doesn't work because expects($this->once())
will fail on the second call.
$mock->expects($this->once()) ->method('foo') ->with('someValue'); $mock->expects($this->once()) ->method('foo') ->with('anotherValue'); $mock->foo('someValue'); $mock->foo('anotherValue');
I have also tried:
$mock->expects($this->exactly(2)) ->method('foo') ->with('someValue');
But how do I add a with() to match the second call?
PHPUnit provides methods that are used to automatically create objects that will replace the original object in our test. createMock($type) and getMockBuilder($type) methods are used to create mock object. The createMock method immediately returns a mock object of the specified type.
Stub. Stubs are used with query like methods - methods that return things, but it's not important if they're actually called. $stub = $this->createMock(SomeClass::class); $stub->method('getSomething') ->willReturn('foo'); $sut->action($stub);
You need to use at()
:
$mock->expects($this->at(0)) ->method('foo') ->with('someValue'); $mock->expects($this->at(1)) ->method('foo') ->with('anotherValue'); $mock->foo('someValue'); $mock->foo('anotherValue');
Note that the indexes passed to at()
apply across all method calls to the same mock object. If the second method call was to bar()
you would not change the argument to at()
.
Referencing from the answer from a similar question,
Since PHPUnit 4.1 you can use withConsecutive
eg.
$mock->expects($this->exactly(2)) ->method('set') ->withConsecutive( [$this->equalTo('foo'), $this->greaterThan(0)], [$this->equalTo('bar'), $this->greaterThan(0)] );
If you want to make it return on consecutive calls:
$mock->method('set') ->withConsecutive([$argA1, $argA2], [$argB1], [$argC1, $argC2]) ->willReturnOnConsecutiveCalls($retValueA, $retValueB, $retValueC);
It's not ideal to use at()
if you can avoid it because as their docs claim
The $index parameter for the at() matcher refers to the index, starting at zero, in all method invocations for a given mock object. Exercise caution when using this matcher as it can lead to brittle tests which are too closely tied to specific implementation details.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With