laravel4cookbook

Controller Testing 364
.
This file should be saved as phpunit.xml.
This will get the tests running, and serves as a template in which to start writing our tests. You can
actually see this test case working, by running the following command:
1 phpunit
2
3 PHPUnit 4.0.14 by Sebastian Bergmann.
4
5 Configuration read from /path/to/phpunit.xml
6
7 .
8
9 Time: 76 ms, Memory: 8.75Mb
10
11 OK (1 test, 0 assertions)
.
This test is functional because it only happens after a Laravel instance is spun up, and it doesn’t
care about what state it leaves this application instance in.
Since we haven’t implemented the body of the send() method, it’s difficult for us to know what
the return value will be. What we can test for is what methods (on the mailer’s underlying mail
transport/interface) are being called…
Imagine we’re using the underlying Laravel mail class to send the emails. We used it before we
started optimising the controller layer:
1 Mail::send("emails.post", Input::all(), function($email) {
2 $email
3 ->to("cgpitt@gmail.com", "Chris")
4 ->subject("New post");
5 });