How to Test with Playwright with Debbie O'Brien
Categories: Podcasts , How To Test This?
Software testers can benefit from adopting risk assessment and adopting new testing solutions, such as Playwright, with confidence. A guest, Debbie O’Brien, a leader in modern test automation, shares her experience and expertise in using Playwright to automate testing and improve QA processes.
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-with-Debbie-OBrien-e3drnfk
- Published: 2026-01-19T11:46:44Z
- Duration: 00:31:36
- Author: Mamadou N’diaye
Overview
The podcast explores Playwright, an end-to-end testing and browser automation framework, focusing on its features such as auto-waiting, test isolation, parallel execution, and tools like the Trace Viewer and UI mode which aid in debugging. The discussion highlights Playwright’s integration with AI to support test creation and maintenance, including tools like CodeGen and AI-powered agents that help plan, generate, and update tests. The episode also addresses common pitfalls in test automation, such as overusing timeouts and ineffective locators, and offers strategies to minimize flaky tests.
Additionally, the conversation touches on best practices like using TypeScript for test automation, integrating Playwright with CI/CD pipelines such as GitHub Actions, and the changing role of testers as AI becomes more integrated into testing processes. The importance of practical experience, community involvement, and a genuine passion for test automation is emphasized as essential components for success in the field.
What If
-
What if you integrated Playwright’s CodeGen for rapid test generation in your next project?
Move: Use Playwright’s CodeGen feature to manually interact with a website and auto-generate test scripts.
Why now: With AI-driven tools like CodeGen, you can reduce test creation time by 50-70% and focus on higher-level QA strategy.
Expected upside: Faster test suite development, lower maintenance overhead, and higher test coverage for critical user flows. -
What if you audited your current test suite for flaky tests caused by timeouts or race conditions?
Move: Review all tests for manual timeouts and ambiguous locators (e.g., XPath), replacing them with Playwright’s auto-waiting and built-in assertions.
Why now: Flaky tests cost 30%+ of QA time in legacy systems, and modern frameworks like Playwright are designed to mitigate this.
Expected upside: 30-50% faster test execution, stable CI pipelines, and reduced manual debugging effort. -
What if you deployed Playwright Agents (e.g., Test Planner or Healer) for continuous test maintenance?
Move: Set up the Healer Agent to automatically fix broken tests when elements change, and use the Test Planner to generate test plans from user stories.
Why now: AI agents can reduce test maintenance by 40-60%, and Playwright’s agent ecosystem is mature enough for production use.
Expected upside: 50-70% reduction in test maintenance time, smoother onboarding for new team members, and adaptive test coverage for evolving applications.
Takeaway
- Implement Playwright’s auto-waiting and parallel execution: Use Playwright’s built-in features (e.g., auto-waiting, test isolation, and parallel execution) to streamline test workflows, reduce flakiness, and improve test efficiency for faster feedback cycles.
- Leverage CodeGen for test automation: Use Playwrights CodeGen tool to manually interact with your application and automatically generate test scripts, then refine them with custom assertions to save time on repetitive test creation.
- Avoid overusing manual timeouts: Rely on Playwright’s default auto-waiting and fail-safe mechanisms instead of adding explicit timeouts, which can slow down tests and introduce instability. Only add manual timeouts when absolutely necessary.
- Use Playwright locators over XPaths: Prioritize Playwrights built-in locators (e.g.,
getByRole,getByText) over ambiguous XPaths to ensure test reliability, reduce flakiness, and improve maintenance of test scripts. - Set up CI/CD pipelines with GitHub Actions: Integrate Playwright with GitHub Actions to automate test execution, utilize sharding for large test suites, and use AI-assisted debugging tools like Trace Viewer to analyze failures with screenshots, logs, and network data.
For a PDF of longer Software Testing Podcast Episode Summaries with Briefing Notes and more detailed summary notes, visit EvilTester Patreon Podcast Summaries.