Thanks for the course its take me to the next level as Dev. I have a lazy question? When i started working with tests and watch this course i noticed that i can test many things in my projects like, blade components, controllers, policies, form-requests , routes, rendered views... so i have to test all of that? or i have to focus on test how data flows in my system in each feature of the system requirements. And suggest to make videos about Browse testing in Laravel Dusk many content about are not updated on TH-cam i think. Sorry about my English it's not my native language.
I think in one of the videos I focused on WHAT to test, don't remember which one. Basically, test the CRUCIAL things first: permissions, payments, page loading well, etc. Then you MAY test something else but that's optional. With Laravel Dusk, I'm not a big fan of such visual testing relying on the browser, and the community seems to agree if they don't create/update content about it.
This is very useful thank you for that !
Thank you very much!
Brilliant video
Very interesting and useful, thank you for this.
Thanks for the course its take me to the next level as Dev.
I have a lazy question?
When i started working with tests and watch this course i noticed that i can test many things in my projects like, blade components, controllers, policies, form-requests , routes, rendered views...
so i have to test all of that? or i have to focus on test how data flows in my system in each feature of the system requirements.
And suggest to make videos about Browse testing in Laravel Dusk many content about are not updated on TH-cam i think.
Sorry about my English it's not my native language.
I think in one of the videos I focused on WHAT to test, don't remember which one. Basically, test the CRUCIAL things first: permissions, payments, page loading well, etc. Then you MAY test something else but that's optional.
With Laravel Dusk, I'm not a big fan of such visual testing relying on the browser, and the community seems to agree if they don't create/update content about it.
@@LaravelDaily thanks for explanation.