Too Long; Didn't Read
Imagine you are working on a Laravel side-project or you just joined a team working on a<strong> Laravel application</strong>, and it currently doesn’t have a single <strong>test</strong>. You want to change that, and add tests to the application. If you find yourself in this situation, you might not even know where to start. “Should I unit test everything? Should I just test the most critical parts of the application?” You might even find yourself asking “<strong>Why do I need tests in the first place?</strong>”