Writing Pest Tests for Laravel CRUD: Live-Coding

[@373323]

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

[@jkg_1]

Sir, we need a video about storage, symlinks, storage maintenance. Thanks

[@LaravelDaily]

Ok adding to my to-do list

[@hardiklakhalani6268]

Right. Also seen some codebases with "bucket thing" in such modular way that we can choose where the files get stored.

[@shire7949]

How about "please"

[@fernandolamas330]

awesome lesson!!, huge thanks sr.!

[@drugoviic]

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

[@manojbist3793]

Thanks for the lesson. Can you please make a video on CI/CD using different tools.

[@LaravelDaily]

It's a very broad topic, and each tool is even deeper. So maybe a separate COURSE about it, would you buy it?

[@ziemustdie]

Finally! Thanks so much

[@darkbelg]

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.

[@LaravelDaily]

My rule of thumb is always use route names, no matter the context.

[@holakonoob]

if u have a big app like have 200+ model then its better to like use baseCrudTest class to not repeat it

[@capins85]

Nice explanation as always! I have a doubt: never find a tutorial to test Filament projects. Really don't know how to start

[@LaravelDaily]

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.

[@capins85]

​@@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

[@gdogmalone]

What’s doing your auto completion please? Is that standard or an AI? 10:56 (😂answered at 12 minutes!)

[@vladislavkresta1321]

What if my whole CRUD si based on Livewire so I don't have any POST routes to create User model?

[@LaravelDaily]

In Livewire, tests are different, it's Livewire::test() from what I remember. So read the Livewire docs about testing.

[@vladislavkresta1321]

@@LaravelDaily Great, looking forward it, thanks for your quick reply, appreciate it!

[@gilney.mathias]

Now do this on a 10+ years old legacy project 😭

[@LaravelDaily]

Mission impossible.

[@trap7369]

@@LaravelDaily 😂😂😂

[@lyrihkaesa]

Can you explain how to test laravel dusk + pest on select filament search.

[@LaravelDaily]

Haven't used that exact combination, so can't explain, sorry.