laravel4cookbook

Controller Testing 362
14
15 public function insert()
16 {
17 $data = [
18 "title" => $this->request->get("title"),
19 "subtitle" => $this->request->get("subtitle"),
20 "body" => $this->request->get("body"),
21 "author_id" => $this->request->get("author"),
22 "slug" => Str::slug($this->request->get("title"))
23 ];
24
25 // insert posts with $data...
26 }
.
This was extracted from app/Formativ/PostRepository.php.
Using this approach, you can delegate method calls based on events, rather than explicit method
calls and variable manipulation.
.
There are loads of different ways to use events, so you should definitely check out the official docs
at: http://laravel.com/docs/events.
http://laravel.com/docs/events
This Isn’t Testing!
If you’re wondering how this is related to testing, consider how you would have tested the original
controller code. There are many different responsibilities, and places for errors to emerge.
Splitting off your logic into classes of single responsibility is a good thing. Generally following
SOLID principles is a good thing. The smaller your classes are, the fewer things each of them do,
the easier they are to test.
So how would we write tests for these new classes? Let’s begin with one of the concrete implementations: