https://github.com/matthewbdaly/laravel-testing-recipes
https://github.com/matthewbdaly/laravel-testing-recipes
Last synced: 3 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/matthewbdaly/laravel-testing-recipes
- Owner: matthewbdaly
- Created: 2017-04-17T20:47:09.000Z (about 8 years ago)
- Default Branch: master
- Last Pushed: 2019-10-06T21:43:03.000Z (over 5 years ago)
- Last Synced: 2025-01-21T07:09:10.381Z (5 months ago)
- Size: 29.3 KB
- Stars: 1
- Watchers: 5
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Laravel Testing Recipes
Laravel is a pretty popular choice of framework right now. It's largely supplanted CodeIgniter as the easiest framework to get started with in PHP, but at the same time it's flexible enough that it can grow with you.
One notable feature of Laravel compared to earlier frameworks such as CodeIgniter is the greater emphasis it places on testing. It comes with both PHPUnit and Mockery installed by default, and the documentation strongly encourages you to write tests for your application. However, that doesn't necessarily mean that it's obvious how to test every component of your application.
That's where this book comes in. Over the last few years I've used Laravel fairly extensively and I've formulated strategies for writing tests for most of the components of a typical Laravel application. I won't pretend this book is exhaustive, but it will give you recipes for testing the major components of your Laravel application. Once this is done, you'll understand the methodology behind writing tests, and the tools used, and will be in a position to start formulating your own testing strategies.
How to read this book
---------------------
This is more of a cookbook than something to be read cover to cover, and my experience has been that it's easier to understand testing by doing than by reading about it. To get the best out of it, I'd recommend the following methodology:
* Skim-read it once, just to get the sense of what it covers.
* Then, when you have the occasion to write a test for something, find the appropriate section, and use that to help you write the test
About me
--------
To this day, I don't really consider myself first and foremost a PHP developer. I came to web development quite late in life - I was previously a clerical worker before I started to make plans for a new career in my late 20's. I always planned to work first and foremost with Python, specifically the Django framework, but things didn't quite work out that way as PHP is much more prominent where I live. My first web development job was doing PHP development for an e-commerce site, and there I started using CodeIgniter. I later moved on to work at a busy digital agency doing web and Phonegap app development, and I initially stuck with CodeIgniter, although I later started using Django as well.
In 2015 we had another developer join and it became obvious that we needed to make a decision regarding what framework we used by default. I couldn't justify continuing to use Django because none of the other developers knew Python, but at the same time CodeIgniter wasn't up to scratch - its future was uncertain and it had fallen behind the times. I'd been following Laravel with interest for some time, and was already using it on a project. In addition, the developer we'd just hired had also used it, so it was a logical choice.
Since then, there have been many projects I've worked on using Laravel. After moving to a new role, I've taken on a large Laravel legacy project and added tests to it retrospectively. I've tested API's, front ends, and just about everything in between, and I've learned a tremendous amount in the process. Now, hopefully I can help you avoid some of the problems I experienced during that time.