Lucas and Luna examine the discipline of software testing as a strategic function, not a checkbox. Each episode focuses on a specific testing practice — from unit test coverage metrics and integration test design patterns to the economics of test automation ROI and the psychology of flaky test triage. They walk through real-world case studies: how Stripe reduced regression defects by 40% with contract testing, the trade-offs between Selenium and Cypress for e-commerce checkouts, and why Google's test size taxonomy (small/medium/large) forces better architectural decisions. Lucas explains the math behind mutation testing scores and the diminishing returns of 100% code coverage; Luna challenges him on how to sell testing budgets to skeptical product managers and when manual exploratory testing still outperforms automation. They also explore testing philosophies — shift-left vs. shift-right, risk-based testing prioritization, and the role of AI in generating test oracles. The listener leaves each episode with a specific framework or heuristic: how to evaluate a test suite's health, when to kill a test, or how to design a QA career path that doesn't plateau. No generic advice — just the numbers, the names, and the debates that shape reliable software. What does it actually take to build a testing culture that prevents defects instead of just catching them?

Support FexingoRSS Feed