Laravel Testing 101
Last updated on 2019-03-04
About the Book
Imagine you are working on a Laravel side-project or you just joined a team working on a Laravel application, and it currently doesn't have a single test. 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 “Why do I need tests in the first place?”
My main goal with this ebook is to try to answer these questions, and I will describe my process in writing tests for some of the Laravel applications I’m working on (mainly CRUD applications).
As someone who agrees with Guillermo Rauch's quote "Write tests. Not too many. Mostly integration", this book from Youghourta does explain integration tests in a practical manner, if you finally want to embrace tests in your project without feeling you're wasting your time, you'd be serious about this book.
Full-stack Web Developer
It's very practical, showing and assuming how a real world application would change over time and how testing would help mitigate errors that might happen. I also like how the author didn't just throw couple tests and walked away, but he stayed and did refactoring on the tests and showed us how it should be done then integrated everything with a Continuous Integration tool.
Majda Nafissa Rahal
Associate Director, Shift'IN
Testing always seemed intimidating to me. With this ebook, Youghourta does a great job demystifying all of its concepts and breaking them down into digestible, easy-to-understand chapters. I recommend this ebook for anyone looking for an intro to the world of testing in Laravel.
- Why we are writing fewer tests than necessary
- Why do we need tests in the first place?
- So, what should I be testing exactly?
- Structure of the ebook
- What should we be testing in a Laravel CRUD application?
Writing tests for guest user functionalities on a Laravel CRUD application
- Make sure that PHPUnit is working properly with your application
A guest could see all the articles when visiting
- A guest could see a single article
- A guest could see a user profile
- A guest could not write a new article and gets redirected to the signup page instead
- A guest could visit and get the signup page and + A guest could visit and get the login page
- How would tests detect breaking changes in the code base?
Testing what signed up users could do on the application
- A user could write an article
- The user could visit and get the “new article” form
- The user should be able to save the newly created article.
- A user could edit her own articles
- The user could visit and get the “edit article” form
- The user should be able to save the updated article
- A user could delete her own articles and get redirected to the all articles page with a success message
Testing what a logged in user is not allowed to do
- A user should not be able to edit articles she doesn’t own
- A user should not be able to delete articles she doesn’t own
- A user should not be able to create or update articles that bypass the validation rules (short titles and/or short bodies)
Refactor the tests and create a base test class
- Create a base test class
Dealing with test data
- Using a dedicated database
- Exclude the test database from your version control
Set up a Continuous integration tool
- Set up Bitbucket pipelines
The Leanpub 45-day 100% Happiness Guarantee
Within 45 days of purchase you can get a 100% refund on any Leanpub purchase, in two clicks.
See full terms...