good stuff, some subjects like this one for example have a lot of detail and deserve a longer video rather than getting chopped up or simplified to oblivion
What exactly you want to test in Filament? Forms/tables are internally tested in core, and if you want to test on top, it's mostly Livewire testing, and it's all in the docs.
@@LaravelDaily It's complicate to answer you briefly: I learn Laravel with your video and courses, so I educate myself to "Separation of concern", "Stay consistent" and to test features, using controllers methods as a kind of schedule. So with Filament I feel myself a little bit confused: I love to have dashboard ready without losing time with styling, but sometimes I'm not pretty sure to have the control of what i'm doing, I feel like if I repeat code in many places, I don't find the same keystone that you give me with plain Laravel. Maybe should be intresting a series of code reviews about filament! I think that I get the best lessons from your code reviews
Should you use route names in tests? If you have a stand alone vue app. You can change the laravel urls and the tests will still show green. While your vue app will just fail or any external api.
I'm new to testing and have a question. Do I need to write tests for all endpoints in a CRUD? For instance, why should I test the display of the index or create pages when I can manually test them in the browser?
You can test them manually once when you create them but who will test if those pages still work after some other developers make any changes in the future? (which are not necessarily about those pages but may affect them)
good stuff, some subjects like this one for example have a lot of detail and deserve a longer video rather than getting chopped up or simplified to oblivion
Sir, we need a video about storage, symlinks, storage maintenance. Thanks
Ok adding to my to-do list
Right. Also seen some codebases with "bucket thing" in such modular way that we can choose where the files get stored.
How about "please"
Finally! Thanks so much
awesome lesson!!, huge thanks sr.!
I always create a .env.testing and use that to set my preferred database for testing i.e if youre using some sql methods unavailable in sqlite
Thanks for the lesson. Can you please make a video on CI/CD using different tools.
It's a very broad topic, and each tool is even deeper.
So maybe a separate COURSE about it, would you buy it?
Nice explanation as always! I have a doubt: never find a tutorial to test Filament projects. Really don't know how to start
What exactly you want to test in Filament? Forms/tables are internally tested in core, and if you want to test on top, it's mostly Livewire testing, and it's all in the docs.
@@LaravelDaily It's complicate to answer you briefly:
I learn Laravel with your video and courses, so I educate myself to "Separation of concern", "Stay consistent" and to test features, using controllers methods as a kind of schedule.
So with Filament I feel myself a little bit confused: I love to have dashboard ready without losing time with styling, but sometimes I'm not pretty sure to have the control of what i'm doing, I feel like if I repeat code in many places, I don't find the same keystone that you give me with plain Laravel.
Maybe should be intresting a series of code reviews about filament! I think that I get the best lessons from your code reviews
Should you use route names in tests? If you have a stand alone vue app. You can change the laravel urls and the tests will still show green. While your vue app will just fail or any external api.
My rule of thumb is always use route names, no matter the context.
if u have a big app like have 200+ model then its better to like use baseCrudTest class to not repeat it
I'm new to testing and have a question. Do I need to write tests for all endpoints in a CRUD? For instance, why should I test the display of the index or create pages when I can manually test them in the browser?
You can test them manually once when you create them but who will test if those pages still work after some other developers make any changes in the future? (which are not necessarily about those pages but may affect them)
Which testing framework is better to learn for a developer who is new to testing: Pest or PHPUnit?
If you're planning to work with Laravel projects, then Pest. If your plan is with general PHP projects or other frameworks, then phpunit.
What’s doing your auto completion please? Is that standard or an AI? 10:56 (😂answered at 12 minutes!)
What if my whole CRUD si based on Livewire so I don't have any POST routes to create User model?
In Livewire, tests are different, it's Livewire::test() from what I remember. So read the Livewire docs about testing.
@@LaravelDaily Great, looking forward it, thanks for your quick reply, appreciate it!
Do you do contract/consulting work?
No, not anymore, focused on content full-time.
Now do this on a 10+ years old legacy project 😭
Mission impossible.
@@LaravelDaily 😂😂😂
Can you explain how to test laravel dusk + pest on select filament search.
Haven't used that exact combination, so can't explain, sorry.