Pest v4: AI-Assisted Test Generation and Native Browser Automation

Host: Alex Chan Hey everyone, welcome back to Allur, your home for all things PHP, Laravel, and the broader world of modern development. I’m your host, Alex Chan, and today we are talking about something that—honestly—used to be the part of the job everyone procrastinated on. We’re talking about testing. But specifically, we’re talking about how the "chore" of testing is being turned into a superpower. Host: Alex Chan To help me break this all down, I am joined by Oliver Vance. Oliver is a Lead Engineer at SparkScale and a long-time contributor to the Laravel community. He’s been battle-testing v4 since the early alphas and has some really interesting stories about how it’s changing his team’s workflow. Oliver, welcome to Allur! Guest: Oliver Vance Thanks so much for having me, Alex! It’s great to be here. I’ve been listening to the show for a while, so it’s a bit of an "aha" moment for me to actually be on the other side of the mic. Host: Alex Chan Oh, I love that! Well, we’re glad to have you. So, Oliver, let’s jump straight into the deep end. Pest v4 just dropped, and the big headline is the migration to the PHPUnit 12 engine. For the average dev who just wants their green checkmarks in GitHub Actions, why does that engine upgrade actually matter? Guest: Oliver Vance It’s a huge deal, actually. I think sometimes we see version numbers and just think, "Oh, another update," but PHPUnit 12 is a massive leap. Moving Pest to that engine means we’re getting full, native support for PHP 8.x features. But the real "wow" factor for me has been the memory management. In older versions, as your test suite grew—say you have three, four thousand tests—you’d start seeing your CI pipeline slow down or even crash because of memory leaks. PHPUnit 12, and by extension Pest v4, is just... leaner. It’s faster, it’s more stable, and it sets the stage for all the crazy "smart" features Nuno and the team added. Host: Alex Chan Speaking of "smart" features... we have to talk about the elephant in the room. AI. Pest v4 is introducing experimental AI-assisted test generation. Now, my first thought—and maybe some of our listeners are thinking this too—is: "Is this going to write bad tests that I then have to spend an hour fixing?" What’s been your experience with the `pest:generate-tests` command? Guest: Oliver Vance (Laughs) That’s a totally fair concern. Look, we’ve all seen AI hallucinations. But here’s how I look at it: the hardest part of testing is often the blank page. You write a complex `UserRegistrationService` and you think, "Okay, I need to test the validation, the database persistence, the welcome email, the edge cases..." and it’s exhausting just to start. Host: Alex Chan That’s a really interesting way to put it—overcoming the "blank page" problem. It’s like the AI gives you a head start so you can focus on the tricky logic. But let's move to something that has historically been... well, a bit flaky. Browser testing. In the past, I’ve used Laravel Dusk or tried to hook up Selenium, and it’s always felt like a separate world from my unit tests. Pest v4 is bringing browser automation *native* into the framework. How does that change the day-to-day? Guest: Oliver Vance Oh, Alex, this is probably my favorite part. The "context switching" is what used to kill my productivity. I’d be writing these beautiful, short Pest tests for my models, and then I’d have to switch to a completely different syntax and configuration for my end-to-end tests. Host: Alex Chan I saw a code snippet where it looks like you just chain methods—like `->visit()`, `->type()`, `->press()`. It almost looks too simple to be true! Guest: Oliver Vance Right?! It’s almost dangerous how easy it is. You start wanting to test *everything* in the browser. But that’s where the "Deep Quality Assurance" part of v4 comes in, which prevents you from just having "lazy" tests. Host: Alex Chan Actually, that’s exactly where I wanted to go next. You mentioned Mutation Testing. I’ll be honest, when I first heard that term, it sounded like something out of an X-Men movie. Can you explain—in plain English—what mutation testing is and why Pest v4 making it a first-class citizen is a game-changer? Guest: Oliver Vance (Laughs) Totally. No capes involved, unfortunately! So, normally we talk about "Code Coverage." You see that green bar that says "80% Coverage" and you feel good. But code coverage only tells you that a line of code was *executed*. It doesn't tell you if your test actually *checked* anything on that line. Host: Alex Chan Wait, that’s wild! So it’s basically testing the *quality* of the tests themselves? Guest: Oliver Vance Exactly. It moves the goalpost from "Did I run this code?" to "Would I notice if this code broke?" It’s been a huge "aha" moment for our team. We had some files with 100% coverage, but when we ran mutation testing, we realized that if someone changed a crucial piece of logic, our tests would stay green. That’s a scary thought! Pest v4 brings this right into the CLI, so it’s not some academic exercise anymore. It’s actionable. Host: Alex Chan That sounds like it could be a bit humbling for some developers! To see that your "perfect" test suite is actually full of holes. Guest: Oliver Vance Oh, it definitely is. There were some bruised egos the first week we turned it on, myself included. But honestly, the peace of mind you get after you "kill all the mutants" and your tests are actually bulletproof? It’s worth it. Host: Alex Chan So, if a developer is listening to this and they’re still on Pest v2 or v3, or—heaven forbid—they’re still writing old-school PHPUnit tests and feeling a bit overwhelmed, what’s your advice? Is v4 the right time to make the jump? Guest: Oliver Vance Honestly, yeah. The migration path is really smooth, and the benefits—especially the speed and the AI help—pay for themselves in the first week. If you’re worried about AI, just don’t use that command yet. But the native browser testing and the PHPUnit 12 performance gains are reason enough. It’s not just a tool anymore; it’s like a whole quality-of-life upgrade for your development environment. Host: Alex Chan I love that. "Quality-of-life upgrade." Well, Oliver, thank you so much for sharing your experience. You’ve definitely convinced me to go and refactor a few of my older projects this weekend. Guest: Oliver Vance My pleasure, Alex! Just watch out for those mutants! Host: Alex Chan (Laughs) I will! Host: Alex Chan That was Oliver Vance, diving deep into the world of Pest v4. To recap: we’re looking at a faster engine with PHPUnit 12, AI that helps you get over that initial "testing writer's block," native browser automation that keeps you in the flow, and mutation testing to make sure your tests actually mean something.