Episode 6: Did Playwright Win the AI Testing War?Playwright has quickly become one of the most talked-about tools in test automation. But has it actually won the AI testing war? In Episode 6 of AI First Engineering, Jon Robinson sits down with Andrew Knight, the Automation Panda, to explore why Playwright has gained so much momentum, how AI is changing test automation, and what this means for teams still working with Selenium. The conversation goes beyond the Playwright vs. Selenium debate and looks at test maintenance, developer experience, AI-assisted automation, mobile testing, and the increasingly important build vs. buy question. In this episode, we discuss:• Why Playwright is gaining momentum and how its developer experience and AI integrations are influencing adoption. • Whether Selenium teams actually need to migrate to Playwright, or whether existing reliable and maintainable frameworks can continue to serve their needs. • How AI is changing the way tests are created and maintained, and why standardized frameworks can make it easier for AI to work effectively. • Where Playwright fits in web and API testing, and where teams still need other tools for native mobile testing. • Why test maintenance remains a major challenge with highly customized Selenium frameworks. • Build vs. buy: When does building your own automation infrastructure stop making sense? Andrew discusses friction points including orchestration, execution resources, reporting, dashboards, and devices. • How AI could change the role of testing, with testing potentially becoming more of a shared responsibility across engineering and product teams. • Whether acceptance and evaluation could become increasingly important as teams rethink how quality is owned. About Andrew KnightAndrew Knight, known as the Automation Panda, has spent his career in software testing, quality, and automation. He started as an SDET and progressed into team leadership across multiple companies and industries. He has contributed to open source, including Boa Constrictor, a .NET implementation of the Screenplay pattern. Andrew has also worked in developer relations at Applitools and served as Director of Test Automation University. Today, he is Senior Director of Product and Engineering at Cycle Labs, building test automation solutions for supply chain and warehouse management systems. He is also a Playwright Ambassador, speaker, and educator focused on test automation, Playwright, AI, and software quality. Find Andrew🌐 Automation Panda: automationpanda.com 🌐 Auto Panda Motive: autopandamotive.com 💼 LinkedIn: Andrew Knight / Automation Panda 📚 LinkedIn Learning: Playwright and AI courses Key Takeaways• Playwright's developer experience and AI integration have helped drive its growing momentum. • Teams with reliable Selenium automation do not necessarily need to rewrite it. • AI can accelerate test creation and maintenance, but the underlying framework and consistency still matter. • Playwright is focused primarily on web testing and does not replace native mobile testing. • Build vs. buy depends on a team's skills, infrastructure, scale, orchestration, reporting, and execution needs. • AI may reduce manual testing work while making quality expertise and judgment more important. Listen to Episode 6 of AI First Engineering: Did Playwright Win the AI Testing War?
