laravel4cookbook

Controller Testing 367
43
44 return true;
45 });
46 }
47
48 protected function getMailerMock()
49 {
50 return Mockery::mock("Illuminate\Mail\Mailer");
51 }
52 }
.
This file should be saved as app/tests/Formativ/PostMailerTest.php.
Phew! Let’s break that up so it’s easier to digest…
1 Mockery::mock("Illuminate\Mail\Mailer");
Part of trying to test in the most isolated manner is substituting dependencies with things that
don’t perform any significant function. We do this by creating a new mock instance, via the
Mockery::mock() method.
We use this again with:
1 $emailMock = Mockery::mock("stdClass");
We can use stdClass the second time around because the provided class isn’t type-hinted. Our
PostMailer class type-hints the IlluminateMailMailer class.
We then tell the test to expect that certain methods are called using certain arguments:
1 $emailMock
2 ->shouldReceive("to")
3 ->atLeast()
4 ->once()
5 ->with("foo");
This tells the mock to expect a call to an as-yet undefined to() method, and to expect that it will be
passed “foo” as the first (and single) argument. If your production code expects a stubbed method
to return a specific kind of data, you can add the andReturn() method.
We can provide expected callbacks, though it’s slightly trickier: