Why Every Laravel App Should Use Pest As a Test Runner--Even If Using PHPUnit Syntax

[@guillermocava3568]

0:00 - Intro
0:51 - Overview of back ported features
3:12 - 3 additional flags (profile | parallel | coverage)
4:50 - Switching to Pest
5:44 - Type coverage plugin
6:18 - Expectation API
7:45 - Outro

[@dsuess]

Thank you so much! Was looking to see if it's worth while to change over to Pest. Most of the threads are literally hating just to hate, not giving objective answers. These 8 minutes is what I needed to see.

[@citricguy]

Ok, PEST is awesome. I'm in.

[@havokgames8297]

Would be interested to know your reasoning behind the things you said “aren’t your thing @

[@MattStauffer]

I don't think test coverage is nearly as meaningful of a metric as most people think. What matters is that a human being can agree that the things that matter--as I often say, the things that might lose you your job, or might put your company in the newspaper for the wrong reasons--are covered by tests. Or, in another way of looking at it, that I can refactor or make changes with confidence that I'm not breaking something. % code coverage doesn't give this confidence.
Similarly, I don't think type coverage is a sign of a good or stable application.

[@mokhosh]

Fix focus on camera should help if you’re not moving forwards and backwards

[@MattStauffer]

I know!! I just moved offices and a bunch of buttons got pressed on my camera accidentally… Including the wrong focus settings. 🤦

[@mokhosh]

@@MattStauffer happens to the best of us