More Software Testing Unleashed episodes
Published 2 Apr 2026
Duration: 00:21:56
Python offers broader flexibility for non-web and infrastructure testing with Playwright but requires extra setup, while TypeScript provides native integration with advanced web-specific tools like visual regression testing and Electron/mobile support, making the choice depend on project needs and team expertise.
In this episode, I talk with Maciej Kusz, program chair of the Testwarez conference in Poland, about why Playwright doesn't have to mean TypeScript. M...
The podcast discusses the comparison between Python and TypeScript as programming languages for test automation using the Playwright framework. It highlights TypeScript's advantages, such as integrated test runners, comprehensive documentation, and built-in features like visual regression testing and support for Electron and mobile applications. TypeScript's alignment with front-end development workflows and its native type system make it a strong choice for web-focused projects. Python, while lacking some of these integrated tools, is praised for its flexibility in testing a broader range of applications, including hardware, infrastructure, and performance testing. Python's use of PyTest as its test framework simplifies setup for those already familiar with it, though it may require additional plugins for advanced features like async support or reporting. The discussion emphasizes that Pythons versatility and ease of debugging make it suitable for teams prioritizing general-purpose testing, while TypeScript excels in web-specific scenarios with its deep tooling and ecosystem.
The technical comparison also addresses setup complexity and tooling differences. TypeScript benefits from pre-integrated features like Visual Studio Code plugins for debugging and reporting, while Python relies on external libraries for similar functionalities, which may be less maintained or stable. Both languages share similarities in Playwright code structure, reducing the need for language-specific community resources. However, TypeScripts native type handling contrasts with Pythons requirement for type annotations. The podcast concludes that the choice between the two depends on project requirements, team expertise, and tooling preferences, with Python offering broader flexibility and TypeScript providing specialized web capabilities. Additionally, Playwrights success is attributed to its stability features like auto-waiting, modern tooling such as Code Gen and Trace Viewer, and its bundled browser management, positioning it as a successor to legacy tools like Selenium.
21 May 2026 Why Testers Are Safe Despite AI Hype - Mitko Mitev
Software testing evolves with automation, agile, DevOps, and AI, but human expertise remains critical due to AI's limitations in context, business logic, and user behavior, shifting testers toward strategic roles while AI aids in repetitive tasks and efficiency.
23 Apr 2026 Why Your CI Pipeline Is Lying to You - Simon Stewart
Flaky tests in CI/CD pipelines undermine reliability by causing intermittent failures due to shared state, timing issues, and environmental inconsistencies, requiring strategies like test exclusion, ownership, and prioritized fixes, alongside prevention through rigorous pre-CI testing and layered approaches, while AI aids debugging but not replacement, emphasizing iterative improvements over emotional attachment to code.
16 Apr 2026 From Nokia to iPhone: What Pen Testers Learned - Bartosz Czernic-Goawski
The historical evolution of mobile security, from unencrypted analog systems to 5G cryptography, highlights enduring vulnerabilities like app flaws, IoT risks, user behavior threats, platform security trade-offs, and the ongoing tension between innovation, usability, and privacy.
9 Apr 2026 Empowering Women in Software Testing - Line Ebdrup Thomsen
Highlighting women's underrepresentation in tech's software development versus higher presence in testing due to diverse entry paths and alignment with creativity, while addressing gender bias, stereotypes, and microaggressions, and emphasizing inclusive practices, non-technical skills, and leveraging testing's collaborative nature for growth.
26 Mar 2026 Stop the blame, keep the learning - Natalia Romanska
Learning from failure drives professional growth through objective analysis, a "fail-fast, learn-quick" mindset, self-reflection, feedback, balancing technical and soft skills, avoiding comparisons, and embracing failure's inevitable lessons.