Laracon IN 2023: The future of PEST
HTML-код
- Опубликовано: 9 мар 2023
- This year, it's time to take your testing to the next level with Pest v2.x! With new powerful plugins, improved syntax, and advanced options, Pest v2.x makes testing easier, more user-friendly, and more productive than ever before.
Get ready for a live coding session of Pest v2.x in action with a real-world Laravel project. After this talk, you'll gain a better understanding of how to use Pest v2.x to its full potential. 
Развлечения
Pest drives me to write more tests each and every time. Love the simplicity. Thanks for all your efforts, Nuno.
Arch - Test Examples - Timestamps
13:06 - arch plugin intro
17:15 - make sure controllers only use FormRequests and not request directly
19:46 - make sure models can be used directly only from repositories
22:26 - models to only use illuminate database
24:26 - make sure you never ship 'dd' or 'dump' to production
Take a bow, Nuno . You have solved an age old and a very complex problem of people not following one consistent architecture in a project. It used to make projects un-manageable few years down the line. This is going to be ground breaking.
This was the first talk of second day where everyone felt amazing and refreshed
Its an awesome talk. Nuno Maduro is awesome.
Thank you nuno 🤝, i am the one who watched this live and watching it again 😊
Incredible work and presentation Nuno! Thanks for everything you do to help the community ❤
Nuno ! Nuno ! 😂ahah top , those guys are amazing. Great talk Nuno as always.
O monstro do php
Excelente! Continue a postar os conteúdos, aprendo muito com suas palestras 😃
Very very nice Nuno! Well done :)
You are a god! Thank you so much.
Sublime.
Can't wait 😍
For me it looks more like JS unit tests instead of PHP, but looks cool. The more advance features are pretty awesome (ex: arch part).
What test framework he used when he test the PEST?
Why cannot be installed yet to Laravel 10 giving an error related to nunomaduro/collision[v5.10.0, v5.11.0, v5.x-dev, v6.0.0...]
19:11 if that's the demo-worthy example there, then it's not that great of a plugin. The issue lies in the fact that you had to remove that import - you could still keep it there and actually utilize the form request class but it would still fail for, mostly, unoptimized imports, which means - we would have to communicate with the team to either use a save hook to optimize imports or at least hit ctrl+alt+o to do so (by default shortcut). Though it would be normal for us to forget that which makes this plugin to have prerequisits otherwise it's too brittle of an implementation. Or, frankly, that plugin could be "avoided" by using FQDN when using the model/request/other class.
Just my 2 cents.
I saw it too but removing the imports isn't that big off a deal and if you're using this you're already going to have to talk to your team