Testing your laravel apps
Draft Disclaimer: Please note that this article is currently in draft form and may undergo revisions before final publication. The content, including information, opinions, and recommendations, is subject to change and may not represent the final version. We appreciate your understanding and patience as we work to refine and improve the quality of this article. Your feedback is valuable in shaping the final release.
Language Mismatch Disclaimer: Please be aware that the language of this article may not match the language settings of your browser or device.
Do you want to read articles in English instead ?
testing manual testing vs automated testing TDD as my goto way Testing in laravel Some usual tests
- units not required
- features
- smoke very helpful
- adding to the helpful but not required testing
- Php is an interpreted language which means
Wrap up
unless you're a hardcode tester, you wouldn't consider the helpful tests as required. Nevertheless, you wouldn't lose much trying it out. The effort / gain ratio is good. At times, I had my route:list broken (because of some refactoring) but I wouldn't know about it
Caveat
- automated testing so I rely 100% on it
- test but remember your tests are code which means your tests can contain bug more often you would imagine.
- random thought: write tests that cover the tests that test the code... Don't know if that exists but that is not for me.
