Lucas and Luna dig into test flakiness — tests that fail without any code change. They break down why flaky tests destroy developer trust, waste hours of CI pipeline time, and silently undermine entire QA strategies. Lucas cites real data: Microsoft's 2014 study found 14% of test failures are flaky, and a 2023 Google survey showed teams spend 10–30% of sprint time re-running and debugging false failures. The hosts walk through practical root causes: async timing, test ordering dependencies, and brittle environment assumptions. Luna challenges Lucas on whether most teams even track flakiness. They close with a concrete playbook: quarantine flaky tests, measure flaky-failure rate per build, and set a 2% threshold for blocking deploys. A must-listen for any engineering team shipping software in 2026.

#TestFlakiness #ContinuousIntegration #QABottlenecks #MicrosoftResearch #FlakyTests #DeveloperProductivity #CIPipeline #TestAutomation #ReliableSoftware #SoftwareEngineering #TestDebt #EngineeringCulture #GoogleSurvey #AgileTesting #TestStability #Technology #FexingoBusiness #BusinessPodcast

Keep every episode free: buymeacoffee.com/fexingo

Episode 12 of Software Testing with Fexingo examines why the quality of test data often matters more than the volume of test cases. Lucas and Luna dive into the 70-30 rule—70 percent of test failures trace back to data issues, not code bugs—using the 2024 CrowdStrike outage as a real-world case study. They discuss how synthetic data generation, production-like datasets, and data versioning can prevent false positives and missed defects. The episode also covers practical strategies for maintaining test data hygiene, including data subsetting and masking, to ensure your test suite actually validates the right things. A must-listen for QA engineers, automation leads, and engineering managers who want to reduce flaky tests and improve release confidence.

#TestDataQuality #SoftwareTesting #QA #TestAutomation #DataHygiene #CrowdStrike #SyntheticData #TestCoverage #FlakyTests #DataVersioning #TestEnvironments #SoftwareEngineering #Technology #FexingoBusiness #BusinessPodcast #EngineeringManagement #DevOps #DataMasking

Keep every episode free: buymeacoffee.com/fexingo

In this episode of Software Testing with Fexingo, Lucas and Luna tackle a problem that derails even the best test suites: unreliable test environments. Lucas explains why environment drift is the silent killer of test validity, using a case study of a fintech startup where 40% of test failures were false alarms caused by configuration mismatches. They discuss practical strategies like infrastructure-as-code, environment tagging, and the concept of 'golden images' to keep dev, staging, and production aligned. Luna challenges Lucas on the cost of maintaining multiple environments, and Lucas responds with data showing the return on investment from reducing false positives. If your tests pass locally but fail in CI, this episode is for you.

#TestEnvironment #EnvironmentDrift #InfrastructureAsCode #GoldenImages #SoftwareTesting #QA #TestAutomation #DevOps #ConfigurationManagement #FalsePositives #Fintech #TestValidity #CI #Technology #SoftwareEngineering #FexingoBusiness #BusinessPodcast #TestingStrategy

Keep every episode free: buymeacoffee.com/fexingo

In episode 10 of Software Testing with Fexingo, Lucas and Luna dive into the concept of testability as a design principle, not an afterthought. They dissect how code written without testing in mind creates hidden costs—longer debug cycles, flaky suites, and fragile refactors. Lucas introduces the concrete example of a fintech startup whose QA velocity doubled after enforcing dependency injection and interface segregation. Luna challenges him on whether testability can be retrofitted, and they walk through a real-world case of a legacy monolith that was gradually untangled. The episode closes with a specific checklist for developers and QA teams to evaluate testability before the first pull request. No vague platitudes—just actionable architecture decisions.

#TestableCode #SoftwareTesting #QAEngineering #TechPodcast #CleanCode #DependencyInjection #DesignPatterns #CodeQuality #FintechCaseStudy #Refactoring #UnitTesting #IntegrationTesting #TestAutomation #SoftwareArchitecture #Technology #FexingoBusiness #BusinessPodcast #DevOps

Keep every episode free: buymeacoffee.com/fexingo

In this episode, Lucas and Luna dive into the overlooked practice of bug taxonomy — categorising software defects by root cause, severity, and occurrence pattern. They explain why most QA teams skip this step, and how a structured taxonomy at companies like Microsoft and Google has cut bug-fix time by up to 30 percent. Using real examples — from a null-pointer crash in a NASDAQ trading engine to a data-corruption bug in a healthcare app — they show how a simple classification system helps teams prioritise, allocate resources, and prevent recurring issues. The conversation also covers how to start small with just a spreadsheet and five categories. If you are a QA lead, test engineer, or developer wondering why the same bugs keep resurfacing, this episode offers a concrete framework to break the cycle.

#BugTaxonomy #SoftwareTesting #QAStrategy #DefectPrevention #Microsoft #Google #RootCauseAnalysis #TestAutomation #SoftwareQuality #BugTracking #TechPodcast #FexingoBusiness #BusinessPodcast #Technology #ContinuousImprovement #DeveloperProductivity #SoftwareEngineering #QABestPractices

Keep every episode free: buymeacoffee.com/fexingo

Lucas and Luna dive into the hidden failure of test coverage metrics. They unpack why hitting 90% line coverage can still let critical bugs slip into production, using a real example from a mid-size fintech company that shipped a payment-calculation error despite excellent coverage. The hosts explain the distinction between coverage as a vanity metric and coverage as a meaningful risk signal, discuss mutation testing as a diagnostic tool, and offer a practical framework for engineering teams to audit their own test suites. Along the way, they touch on the psychology of how developers game coverage targets and why low-coverage code paths sometimes matter more. A focused, actionable episode for QA engineers, engineering managers, and anyone who has ever wondered why their green test suite turned red in production.

#TestCoverage #MutationTesting #QA #SoftwareTesting #FintechBugs #CoverageMetrics #EngineeringCulture #RiskBasedTesting #CodeQuality #ProductionBugs #TestStrategy #DevEx #Technology #FexingoBusiness #BusinessPodcast #QAStrategy #TechLeadership #ContinuousTesting

Keep every episode free: buymeacoffee.com/fexingo

Lucas and Luna explore why most test suites waste resources testing the wrong things. They anchor on a real example: a fintech company that reduced its regression suite by 60 percent after mapping test cases to business risk. The hosts walk through the concept of a risk matrix — plotting feature criticality against failure probability — and show how it changes test prioritization. They discuss trade-offs: what you lose when you stop testing low-risk paths, how to update the matrix as the product evolves, and why this approach is especially relevant in the current regulatory environment. Luna pushes back on the idea that risk-based testing is just a fancy way to skip work. Lucas brings data from a 2025 industry survey showing teams that use risk matrices detect 40 percent more critical defects before release. The episode ends with a concrete first step for listeners who want to try it tomorrow.

#RiskBasedTesting #SoftwareQuality #TestAutomation #QATesting #TechPodcast #RiskMatrix #TestStrategy #SoftwareEngineering #Fintech #RegulatoryCompliance #TestPrioritization #BugDetection #QualityAssurance #ContinuousTesting #TestingMindset #Technology #FexingoBusiness #BusinessPodcast

Keep every episode free: buymeacoffee.com/fexingo

Lucas and Luna dive into flaky tests—software tests that fail intermittently for no apparent code change. They explore why infrastructure instability, not your code, is often the culprit, using a real case from a mid-size fintech company where a failing test traced back to a memory-constrained CI runner. They discuss how to diagnose flaky infrastructure, the role of deterministic test environments, and when investing in containerized CI pays off. Listeners learn concrete steps: capturing infrastructure metadata at test time, setting resource quotas, and using retry budgets wisely. A practical episode for any engineer tired of false-positive test failures.

#FlakyTests #SoftwareTesting #CI #Infrastructure #TestAutomation #QA #DevOps #TestingStrategy #Reliability #Fintech #Containerization #Docker #MemoryConstraints #DeterministicTesting #FalsePositive #TechPodcast #FexingoBusiness #BusinessPodcast

Keep every episode free: buymeacoffee.com/fexingo

In this episode of Software Testing with Fexingo, Lucas and Luna dive into shift-left testing—the practice of moving testing earlier in the software development lifecycle. Lucas breaks down the cost-benefit analysis using a real example from a major fintech company that saved $2.4 million by catching bugs in design phase instead of production. They discuss how traditional testing is like a 'rework loop' while shift-left is 'prevention over inspection.' Luna pushes back on the overhead of writing tests before code exists, and Lucas counters with data from a 2025 Tricentis study showing that each hour of shift-left testing saves eight hours of debugging. They also address the cultural shift needed, including pairing testers with developers and running static analysis on every commit. The episode ends with a forward-looking question on whether AI-assisted test generation will make shift-left even more powerful. Packed with specific numbers, practical tips, and a healthy dose of skepticism, this episode is a must-listen for QA engineers and engineering leaders alike.

#ShiftLeftTesting #SoftwareTesting #QA #TestAutomation #DevOps #CI/CD #CostOfBugs #Tricentis #Fintech #StaticAnalysis #PreventionOverInspection #TestingStrategy #AgileTesting #ContinuousTesting #SoftwareEngineering #Technology #FexingoBusiness #BusinessPodcast

Keep every episode free: buymeacoffee.com/fexingo

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 less reliable. They also discuss practical strategies for measuring what matters, including how one team at a European bank reduced production defects by half after switching from line to condition coverage. A concrete, actionable episode for engineers and QA managers who want test suites that actually catch bugs.

#CodeCoverage #SoftwareTesting #QA #TestAutomation #ReliableSoftware #MutationTesting #LineCoverage #BranchCoverage #FintechBugs #PaymentProcessing #DefectReduction #EngineeringCulture #TechPodcast #FexingoBusiness #BusinessPodcast #SoftwareEngineering #QualityAssurance #TestSuite

Keep every episode free: buymeacoffee.com/fexingo