How To Test With Playwright and Agentic AI with Rex Jones II
Categories: Podcasts , How To Test This?
Test automation has evolved from tools like QTP and Selenium to modern solutions like Playwright, with AI enhancing efficiency while requiring human oversight. Testers must adapt by mastering core programming skills and embracing collaborative roles in guiding automated systems.
How To Test This?
interview episodes where Mamadou N’diaye talks with with software testing experts
- https://podcasters.spotify.com/pod/show/spidey1944
- https://www.youtube.com/@HowToTestThis
- https://www.linkedin.com/in/mamadou-ndiaye-consultant/
Episode Details
- Show Notes: https://podcasters.spotify.com/pod/show/spidey1944/episodes/How-To-Test-With-Playwright-and-Agentic-AI-with-Rex-Jones-II-e3p8sge
- Published: 2026-09-23T01:30:54Z
- Duration: 00:34:50
- Author: Mamadou N’diaye
Overview
The podcast discusses the evolution and current state of test automation, focusing on tools like QTP, Selenium, and Playwright. The guest shares insights into the role of an SDET, emphasizing the importance of combining software development skills with testing expertise. A key theme is the shift from older tools like QTP and Selenium to more modern solutions like Playwright, particularly with TypeScript, due to its efficiency, built-in features such as parallel testing and API support, and user-centric element locating strategies. Comparisons between Selenium and Playwright highlight differences in setup, maintenance, and capabilities, with recommendations based on team needs and existing frameworks.
The discussion also explores the growing impact of AI on test automation, including the use of agentic intelligence to generate test cases and automate scenario creation. While AI accelerates testing processes, human oversight remains critical for validating outputs, applying critical thinking, and ensuring quality. Testers are encouraged to adopt a mindset of continuous learning, focusing on core programming fundamentals - such as variables, data types, and object-oriented programming - and leveraging AI responsibly with proper guardrails. The future of testing is seen as increasingly collaborative, with testers evolving into orchestrators who guide, review, and refine automated systems rather than building tests from scratch.
What If
-
What if you migrated your existing Selenium tests to Playwright using AI as a co-pilot?
- Move: Select a small, critical test suite in Selenium (Java), then use an AI tool (e.g., GitHub Copilot or ChatGPT) to rewrite it in Playwright with TypeScript. Manually review and refactor the output, applying Page Object Model and
getByRolelocators. - Why Now?: Playwright’s modern API and resilience to DOM changes reduce long-term maintenance; AI accelerates migration while preserving your control - ideal for solo developers needing fast ROI.
- Expected Upside: 40 - 60% faster test execution, easier debugging, and a future-proof codebase you can showcase on GitHub to attract clients or employers.
- Move: Select a small, critical test suite in Selenium (Java), then use an AI tool (e.g., GitHub Copilot or ChatGPT) to rewrite it in Playwright with TypeScript. Manually review and refactor the output, applying Page Object Model and
-
What if you built a reusable AI prompt library to generate and validate test cases daily?
- Move: Create a structured set of 5 - 10 prompts (e.g., “Generate edge case scenarios for login with invalid OTP”) tailored to your app. Run them weekly via AI, then manually verify and integrate 2 - 3 high-value cases into your Playwright suite. Tag outputs with
// created by AIfor traceability. - Why Now?: AI-generated test design is maturing fast - solo operators who systematize this gain rapid coverage without scaling headcount.
- Expected Upside: 3x increase in test scenario throughput within a month, with auditable, maintainable additions that strengthen regression suites.
- Move: Create a structured set of 5 - 10 prompts (e.g., “Generate edge case scenarios for login with invalid OTP”) tailored to your app. Run them weekly via AI, then manually verify and integrate 2 - 3 high-value cases into your Playwright suite. Tag outputs with
-
What if you designed your next automation project using Playwright CLI and Healer Agents from day one?
- Move: Start a new micro-project (e.g., testing a personal SaaS landing page) using Playwright CLI to scaffold tests, enable Healer Agent for auto-recovery on flaky locators, and add guardrails (e.g., comment-based change alerts). Avoid Playwright Test MCP to streamline workflow.
- Why Now?: Playwright CLI offers better token management and agent integration - early adoption avoids tech debt and aligns with industry shifts toward autonomous test healing.
- Expected Upside: Reduce locator-maintenance time by up to 70%, demonstrate cutting-edge practices in your portfolio, and build confidence in self-healing systems for client work.
Takeaway
- Learn TypeScript fundamentals before diving into Playwright, as it enables more effective and maintainable test automation.
- Adopt the Page Object Model or similar design patterns when building test suites to improve code reusability and reduce maintenance overhead.
- Use Playwright’s user-centric locators like
getByRoleinstead of brittle selectors (e.g., XPath or CSS) to create resilient tests that withstand UI changes. - Integrate AI tools into your workflow but apply guardrails - such as tagging AI-generated code and manually validating outputs - before merging into the main codebase.
- Build a public GitHub portfolio by completing structured courses and publishing real projects to demonstrate practical skills to employers or clients.
For a PDF of longer Software Testing Podcast Episode Summaries with Briefing Notes and more detailed summary notes, visit EvilTester Patreon Podcast Summaries.