https://leanpub.com/laravel-testing-decoded
Jeffrey Way answers your question in his book, you could also check out the testing lessons on Laracasts.
You should test anything that has a chance to break. But you should not test something that has already been tested. You can test your controllers, that comes down to preference thought.
At my company I have worked on a project that had such a high testincoverage that 75% of the time people where fixing tests and only 25% of time people were writing new features.
Test in isolation to prevent you from that kind of situation.
Sign in to participate in this thread!
The Laravel portal for problem solving, knowledge sharing and community building.
The community