More Software Testing Unleashed episodes
Published 5 Mar 2026
Duration: 2029
Software testing and quality assurance should be framed through economic reasoning to align with organizational goals and demonstrate value to managers.
In this episode, I talk with Vitaly Sharovatov about the economics of testing. We ask how testers can sell quality to managers who think in money, ris...
The podcast emphasizes the need to frame software testing and quality assurance (QA) through economic reasoning to align with organizational goals and managerial key performance indicators (KPIs). It addresses the communication gap between testers and managers, stressing the importance of translating technical risks into quantifiable economic impacts, such as cost savings from defect prevention, reduced operational costs, or minimized customer churn. Real-world examples highlight the financial and reputational damage caused by poor testing in high-profile failures, reinforcing QAs role in mitigating risks. Strategies discussed include leveraging regulatory compliance to justify QA efforts, analyzing customer retention costs, optimizing workflows to minimize rework, and using data-driven metrics to demonstrate QAs value to stakeholders.
The discussion also explores challenges such as sunk cost bias, which can hinder process improvements, and the need for collaboration across departments to refine testing practices. It underscores the balance between standardized QA processes and adaptability to evolving project needs. Ultimately, the focus is on aligning QA strategies with long-term business benefits by using economic arguments, optimizing workflows, and fostering cross-functional collaboration to reduce waste and justify investments in testing as a strategic organizational priority.
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.
2 Apr 2026 The Hidden Playwright Advantage Developers Miss - Maciej Kusz
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.
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.