Laravel Testing 18/24: Test Coverage 'Myth' and What is The Goal Instead?

preview_player
Показать описание

- - - - -
Support the channel by checking out my products:

- - - - -
Other places to follow:
Рекомендации по теме
Комментарии
Автор

Thanks a lot for your time and effort, this is a one-of-a-kind course.🌹🌹

Babaknouri
Автор

Test coverage is just a metric that you should use with other metric on your CI/CD pipeline. When you try to merge new feature to a master branch, some script should try to merge it in a separate docker container, run all the tests and tell you, is your feature is good to merge or not. How to decide if it’s good or not? For example - code coverage should be above 60%. If it’s not - your feature must be rejected. But there are must be other checks too. This will help up to ensure high level of code quality.

maxonfjvipon
Автор

im always trying to get 90%+ of code coverage, for me, its very important

trap
Автор

It doesn't make any sense to spend time on something that I could test much faster in dev. So, at enterprise level (which could be solved with contracts) maybe, but it's a nope for me. Not everyone is an artisan and likes to do the real exiting stuff the slow way.

Btw, I'd love to see your take on the shortcomings of Laravel and when to not use the framework, especially in API projects. That's just as important in my opinion as how to's.

maflones