How to test With Playwright with Qambar Raza
Categories: Podcasts , How To Test This?
Modern software testing evolves with AI and tools like Playwright, reducing runtime and improving reliability, while emphasizing human oversight and quality engineering. Testers should focus on critical thinking, community engagement, and personal branding to enhance their impact and influence product decisions.
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-Qambar-Raza-e3pef0b
- Published: 2026-09-26T22:49:39Z
- Duration: 00:56:26
- Author: Mamadou N’diaye
Overview
The podcast discusses key themes in modern software testing, focusing on the evolution of test automation, the role of AI, and the importance of quality engineering. A major point of discussion is the adoption of Playwright as a powerful, developer-friendly testing framework that enables faster, more reliable test execution. The guest shares real-world benefits from transitioning to Playwright, including a dramatic reduction in test runtime - from 73 minutes to under 7 - and improved team collaboration by aligning test and production code in TypeScript. Emphasis is placed on choosing tools based on team context, writing atomic and independent tests, and avoiding common pitfalls like flaky tests caused by poor application design rather than faulty test logic.
Another core topic is the integration of AI into testing practices, approached as a tool that requires human guidance and constraints. The conversation highlights how uncontrolled AI can generate excessive or irrelevant tests, stressing the need for planning files, prompt engineering, and clear boundaries - similar to mentoring a junior tester. Beyond tools and technology, the discussion underscores the value of critical thinking, personal branding, and community contribution. Testers are encouraged to build visibility through content creation, open-source contributions, and active participation in the testing community, while also developing a quality mindset that influences decisions at all levels of product development.
What If
-
What if you built a public Playwright plugin to solve a recurring testing problem you face daily?
- Move: Identify one repetitive or painful UI testing scenario in your current project (e.g., authentication state persistence, file upload simulation), then build a reusable Playwright plugin with documentation and publish it on npm and GitHub.
- Why Now?: Playwright’s ecosystem is growing rapidly, and niche plugins that solve real problems are highly discoverable - especially by engineering teams adopting modern stacks like TypeScript and Vue.js. Your work will compound visibility and credibility.
- Expected Upside: Establishes technical authority, increases personal brand discoverability (especially via AI-driven recruiter searches), and creates inbound opportunities from developers who depend on your tool.
-
What if you documented your test automation journey using AI-generated summaries guided by human-crafted planning files?
- Move: Create a
plan.mdfor each feature you test - outlining scope, risks, and expected outcomes - then use AI to generate initial test code only within those boundaries, and publish the process as a case study on LinkedIn or a dev blog. - Why Now?: AI tools are flooding testing workflows, but most fail due to lack of constraints. Demonstrating disciplined AI use positions you as a thoughtful practitioner, not just an adopter.
- Expected Upside: Differentiates your skillset in a saturated market, attracts collaboration or job offers from quality-focused teams, and reinforces your own understanding through teaching.
- Move: Create a
-
What if you replaced flaky end-to-end tests with atomic, independent ones - and measured the time saved per sprint?
- Move: Audit your current E2E suite, isolate interdependent or state-leaking tests, rewrite them as isolated units with mocked setups where needed, and automate their execution timing before and after.
- Why Now?: Slow, flaky pipelines directly block solo developer velocity. With Playwright enabling fast parallel runs (as shown in the 73 7 minute example), now is the time to eliminate legacy bottlenecks.
- Expected Upside: Reduces debugging overhead, accelerates local development feedback loops, and delivers measurable ROI (e.g., “cut test runtime by 90%”) that strengthens your value proposition as a solo operator.
Takeaway
- Audit and refactor existing test suites to eliminate flaky tests by identifying application-level race conditions - such as dropdowns loading before data is ready - and replacing arbitrary waits with explicit waits or UI loading indicators.
- Adopt Playwright (or a modern, language-aligned testing framework) when working with contemporary tech stacks like TypeScript or Vue.js to reduce execution time and improve team collaboration through shared codebase practices.
- Create and publish small open-source tools or plugins (e.g., Playwright utilities) to solve specific problems, increasing personal visibility and reinforcing technical understanding through public contribution.
- Develop a focused AI testing workflow using planning files (
plan.md) and constrained prompts to guide AI-generated test cases, preventing redundant outputs and ensuring alignment with actual business requirements. - Build a personal brand by consistently creating and sharing practical content (e.g., YouTube tutorials, blog posts on test automation) optimized with SEO and relevant keywords, while avoiding disclosure of sensitive personal information online.
For a PDF of longer Software Testing Podcast Episode Summaries with Briefing Notes and more detailed summary notes, visit EvilTester Patreon Podcast Summaries.