pest 5.3.0 is out, and it introduces --trace: it uses the playwright GUI to explore the whole history of why a test failed
this was a special request from the @laravel cloud team 🤌🏻 and it's beautiful:
Pest Evals just got a nice upgrade 🚀
pest-plugin-evals now supports Laravel AI v1, including classification models as your eval judge.
So your toBeRelevant(), toBeCorrect(), toBeSafe(), and toSatisfy() evals can be judged using Laravel AI classification.
Faster. Cheaper. Still the same Pest API. 🤝
Laravel Meetup Georgia returns!
@enunomaduro + @NikaJorjoliani (Redberry CTO).
The third slot is open to the community - details to follow!
Oct 8 · 18:00 · Stamba Rooftop
Register: https://t.co/c397nx7DhI
Thanks to @ylynfatt and @laravelnews for highlighting my latest @pestphp package! Let's bring Fuzz testing to PHP!
This article is such a good introduction to the package! 😍
Fuzz for @pestphp made the top spot in the @laravelnews email yesterday!
This was a real treat!
If you haven't tried Fuzz out, go and check it out! https://t.co/j7Gy9JVwGR
Fuzz Testing for PHP on easy mode! 😍
The power of open source is wonderful! I've just released v5.1 of Lawman, the SaloonPHP plugin for @pestphp. This release adds support for @phpstan (which if you're not using, you should be!)
https://t.co/5K65LTKsm2
I've been doing a lot of work with @pestphp browser testing this week with testing our @Shopify apps! It's nice to be able to use the same syntax between frontend and backend tests and it's super powerful! 😍
New website is live: https://t.co/K3tU6u2wEb
I've been building my own products since 2003, mostly alongside client work. Now I'm making a more serious shift, putting my products first.
My main focus right now is https://t.co/b2roO7Tbyj - online galleries built to help photographers sell more. I also plan to launch at least two more products by the end of the year.
Thanks @levelsio for being an inspiration!
We upgraded our website's backend to Pest 5, and the suite came out just as fast as before. Then we turned on @pestphp's TIA. It skips every test your change could not have broken, so the suite goes from something you wait for to something that just runs 👇
https://t.co/NFLURGeY50
Do you run a 15 minute test suite after every commit or do you just leave that to your CI?
We don't think its laziness its more of a broken feedback loop.
When @enunomaduro announced Pest 5 and the TIA engine at @LaraconUS a few weeks ago it really caught our attention.
Pest 5's TIA engine re-runs only the tests affected by what you changed. Everything else replays from cache.
Our internal CRM: 4,016 tests, 79s full suite → 1-2s typical replay.
For a full write-up, real numbers and our honest thoughts checkout our latest post:
https://t.co/Ikvd423WQV
ngl the best thing I did for my frontend tests were to go from testing them with a JS test runner to switching to @pestphp's browser tests.
PHP's testing ecosystem is unmatched.
If you use @pestphp and want to start Fuzz testing your application, I recently released "Fuzz", which helps with exactly that! Check it out on GitHub:
https://t.co/j7Gy9JVwGR
#PHP#SoftwareDevelopment