Software Testing with Fexingo: QA, Automation, and Reliable Software Engineering

Lucas and Luna unpack why code coverage metrics are often misunderstood and misused in QA teams. They focus on a specific case: a mid-size fintech startup that achieved 85% line coverage but still shipped a critical payment-processing bug. The hosts explain the difference between line coverage, branch coverage, and mutation testing, and why chasing a coverage number can actually make your software...

Lucas and Luna explore the gap between passing automated tests and real-world production failures. They examine a 2025 incident at a major payments platform where a green test suite missed a data-race condition under load. The episode unpacks why common testing strategies create false confidence, and introduces concrete techniques like synthetic monitoring and canary deployments that catch what CI...

In this episode of Software Testing with Fexingo, Lucas and Luna dig into why many development teams still ship broken code despite having test automation suites in place. They explore the concept of 'test debt'—accumulated maintenance gaps in automated tests that mirror technical debt in production code. Using a case study from a real fintech startup that faced a critical production outage becaus...

In the debut episode of Software Testing with Fexingo, Lucas and Luna dive into the real-world cost of software failures using a specific, staggering number: $5 billion. They explore the 2018 Knight Capital glitch that lost $440 million in 45 minutes, how Toyota's unintended acceleration bug cost $1.2 billion, and the hidden human cost of bugs in medical devices and aviation. Along the way, they e...