Now this lazy, bundle and defer won my heart. Amazing.

@edvordo Quite helpful, thanks. :)

@javedurrehman Why would you not want your tests in git? How do you share them with your coworkers?

But if you insist, you can still add *.test.php to your .gitignore and the test files will not be in git. This works recursively, so it doesn't matter where your *.test.php file is.

If we create test files in resources/views/pages/post/ then these test pages will also be uploaded in live environment, do you really think that we need to upload them on live project? Since testing files are now spread in multiple files so we can not add .gitignore of /pages directory.

@javedurrehman exactly

I believe Test file should be in the same directory with related files. Easy to read and easy to manage.

@Caleb browser testing is another way of getting confidence on your built app. But yes I think debug is very useful because it happen so instantly that we can't see anything.

There is no doubt Pest is making live easier when testing components of Livewire in Laravel.

@sacha-meunier I do agree with your suggestions but I think when we are using artisan we will need to use make in command when we are actually making new files. I think this is not the change in Livewire but may be a change in artisan. And I think you can also alias your own artisan command as you want, there is option for it in artisan. Such as you can make alias of php artisan serve to pas