Laravel Testing 101

Ressources

Introduction

1. Why we are writing fewer tests than necessary
2. Why do we need tests in the first place?
3. So, what should I be testing exactly?
4. 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

1. Make sure that PHPUnit is working properly with your application
2. A guest could see all the articles when visiting /articles
3. A guest could see a single article
4. A guest could see a user profile
5. A guest could not write a new article and gets redirected to the signup page instead
6. A guest could visit and get the signup page and + A guest could visit and get the login page
7. How would tests detect breaking changes in the code base?
8. Conclusion

Testing what signed up users could do on the application

1. A user could write an article
2. The user could visit and get the “new article” form
3. The user should be able to save the newly created article.
4. A user could edit her own articles
5. The user could visit and get the “edit article” form
6. The user should be able to save the updated article
7. A user could delete her own articles and get redirected to the all articles page with a success message
8. Conclusion

Testing what a logged in user is not allowed to do

1. A user should not be able to edit articles she doesn’t own
2. A user should not be able to delete articles she doesn’t own
3. A user should not be able to create or update articles that bypass the validation rules (short titles and/or short bodies)
4. Conclusion

Refactor the tests and create a base test class

1. Create a base test class
2. Conclusion

Dealing with test data

1. Using a dedicated database
2. Exclude the test database from your version control
3. Conclusion

Set up a Continuous integration tool

1. Set up Bitbucket pipelines
2. Conclusion

Conclusion