In this episode, Lucas and Luna dig into a subtle but devastating class of bugs—state transitions. Most test automation scripts assume the application is in a known state when they start, but real users jump between screens, reload mid-flow, or leave a session open overnight. Lucas explains how a single missing state check caused a major retailer to discount products by 90 percent during a holiday sale, and why the fix wasn't more tests but a state machine model. Luna brings in a healthcare startup story where a broken state machine locked patients out of critical data. They discuss practical patterns: modeling states as explicit enums, using state transition coverage instead of line coverage, and why UI tests should start from a reset state not a cached one. This episode is for QA engineers who have ever seen a test pass in isolation but fail in a suite—and want to know why.

#StateTransitionTesting #TestAutomation #QAEngineering #SoftwareTesting #StateMachines #Bugs #RegressionTesting #TestCaseDesign #FlakyTests #UIDesign #HealthcareTech #RetailTech #CoverageMetrics #TestDrivenDevelopment #ContinuousIntegration #Technology #FexingoBusiness #BusinessPodcast

Keep every episode free: buymeacoffee.com/fexingo

In this episode of Software Testing with Fexingo, Lucas and Luna explain how the Cost of Delay framework can help QA teams decide which tests to automate first. Lucas walks through a concrete example: a fintech app with a login flow, a payment flow, and a reporting dashboard. Using Cost of Delay — calculated as value per unit time — they show why a slow payment test costs $50,000 per week while a login test costs $5,000. They also discuss the four classic delay types: expedite, standard, fixed date, and intangible. Luna pushes back on whether the math is always that clean, and Lucas admits it's a model, not a spreadsheet. This episode is grounded in a real decision-making framework from Don Reinertsen's 'Principles of Product Development Flow' and gives listeners a repeatable method for test prioritization. No fluff, just one practical tool you can use next sprint.

#CostOfDelay #TestPrioritization #QAAutomation #SoftwareTesting #AgileTesting #QAStrategy #Fintech #TestBacklog #DonReinertsen #FlowEfficiency #ValueBasedTesting #RiskReduction #TestAutomationROI #ContinuousTesting #SprintPlanning #Technology #FexingoBusiness #BusinessPodcast

Keep every episode free: buymeacoffee.com/fexingo

Lucas and Luna explore why smoke testing — a lightweight automated check that runs before full regression — is the most underrated safety net in modern CI/CD. Lucas breaks down how one fintech startup cut its rollback rate by 40 percent simply by running a five-minute smoke suite on every deploy candidate. They discuss the difference between smoke tests and sanity tests, the ideal smoke-test ratio (roughly one test per ten API endpoints), and why teams that skip smoke tests often discover broken deploys via user support tickets. Luna pushes back on the notion that smoke tests add pipeline friction, and Lucas shares examples of smoke tests that caught production-breaking Kubernetes config errors within seconds. The episode closes with a look at how smoke tests fit into a broader testing pyramid strategy — and why they should never be treated as a replacement for deep functional coverage. A donation segment draws the parallel between testing safety nets and the listener support that keeps the show ad-free.

#SmokeTesting #CICD #ContinuousDelivery #DevOps #TestAutomation #SoftwareTesting #QualityAssurance #TestingStrategy #DeploymentSafety #BuildPipeline #Kubernetes #FintechCaseStudy #SanityTesting #RegressionTesting #CIBuild #Technology #FexingoBusiness #BusinessPodcast

Keep every episode free: buymeacoffee.com/fexingo

Lucas and Luna dive into visual regression testing — a technique that compares screenshots of your app before and after code changes to catch unintended layout shifts, misaligned buttons, and broken responsive designs. Lucas explains how Twitter (now X) used Percy to catch a critical checkout button misalignment that would have cost millions in lost revenue, and why pixel-perfect testing matters more than ever in the age of frequent front-end deployments. Luna shares a cautionary tale from her own team where a single CSS change broke the entire mobile navigation for two days. They also discuss how teams at companies like Airbnb and Stripe integrate visual regression into their CI pipelines, the trade-offs between pixel-by-pixel comparison and perceptual diffing, and why you should start with your most business-critical user flows. The episode wraps with a brief, honest note about listener support keeping the show ad-free.

#VisualRegressionTesting #SoftwareTesting #QA #Automation #FrontEndTesting #Percy #Twitter #Airbnb #Stripe #CSS #CICD #ResponsiveDesign #PixelPerfect #LayoutBugs #FexingoBusiness #BusinessPodcast #Technology #TestAutomation

Keep every episode free: buymeacoffee.com/fexingo

Most teams waste hours debugging failures that only happen in stale test environments. In this episode, Lucas and Luna unpack why ephemeral environments — spun up per branch, destroyed after merge — are becoming the standard for reliable CI/CD. They walk through how Spotify saved 40 percent of its QA engineers' troubleshooting time by moving to ephemeral Kubernetes namespaces, and why Airbnb's 'one environment per pull request' policy cut its release-blocking bugs by more than half. They also discuss the common objections: cost, complexity, and the fear of losing state. If your team still shares a sticky staging server, this episode gives you the case studies and the counterarguments you need.

#EphemeralEnvironments #TestInfrastructure #CI_CD #QA #SoftwareTesting #DevOps #Kubernetes #Spotify #Airbnb #StagingServer #TestAutomation #EnvironmentManagement #ReliabilityEngineering #Technology #FexingoBusiness #BusinessPodcast #TechPodcast #SoftwareEngineering

Keep every episode free: buymeacoffee.com/fexingo

Flaky tests — those that pass and fail without any code change — waste developer time and erode trust in CI pipelines. In this episode, Lucas and Luna explore why treating flaky tests as purely a code bug misses the real problem: team culture, test ownership, and prioritization. They walk through a typical scenario at a mid-size SaaS company where a flaky API mock causes intermittent failures. Lucas explains how root-cause analysis often reveals test design issues rather than logic errors, and why the best fix is often to delete the test, not debug it. Luna pushes back on the idea that deletion is lazy, and they discuss practical strategies: quarantining flaky tests, setting a team-wide flakiness budget, and using test impact analysis to separate real failures from noise. The episode ends with a forward-looking question about whether AI will solve flakiness or just mask it. Packed with concrete examples and no jargon.

#FlakyTests #TestFlakiness #CI #ContinuousIntegration #TestAutomation #TestOwnership #TestDebt #SoftwareTesting #QA #DevOps #EngineeringCulture #TestPrioritization #Quarantine #FlakinessBudget #RootCauseAnalysis #TechPodcast #FexingoBusiness #BusinessPodcast

Keep every episode free: buymeacoffee.com/fexingo

Mutation testing is one of the most underused techniques in software quality, and it directly answers the question: 'If my code has a bug, will my tests catch it?' In this episode, Lucas and Luna explore how mutation testing works by deliberately introducing small faults—mutations—into your code and checking whether your test suite detects them. They walk through a concrete example with a simple function and show how a 100% line-coverage test suite can still miss critical edge cases. Lucas shares data from a 2025 study at a major fintech firm that found mutation testing revealed 42% of their 'covered' code had undetected bugs. They discuss practical tooling (PIT for Java, mutmut for Python), how to integrate mutation testing into CI without breaking your build, and why aiming for 100% mutation coverage is a trap. The episode closes with a quick reflection on the trade-off between test quality and speed, and a light donation moment tied to the value of a single actionable insight.

#MutationTesting #TestCoverage #SoftwareTesting #QualityAssurance #CI #PIT #mutmut #CodeQuality #TestSuite #Fintech #BugDetection #TechPodcast #FexingoBusiness #BusinessPodcast #Technology #SoftwareEngineering #Automation #TestingTools

Keep every episode free: buymeacoffee.com/fexingo

Episode 36 of Software Testing with Fexingo explores why state management is often the biggest source of elusive UI bugs. Lucas and Luna break down a real-world case: a fintech app that crashed under load because its Redux store wasn't tested for race conditions. They explain how dedicated state management testing differs from traditional unit or component tests, with concrete techniques like action-sequence fuzzing and store invariant checks. The hosts also discuss tools like Redux Toolkit's built-in testing utilities, Zustand's simplicity for smaller apps, and when to use custom middleware to log state transitions. Listeners will learn a practical checklist for writing state tests that catch the kinds of bugs that slip through even thorough integration suites. Plus, a brief behind-the-scenes moment about how listener support keeps the show ad-free.

#StateManagement #Redux #Zustand #Testing #UIBugs #RaceConditions #Frontend #Fintech #JavaScript #ReduxToolkit #Middleware #Fuzzing #Checklist #TestingTools #SoftwareEngineering #Technology #FexingoBusiness #BusinessPodcast

Keep every episode free: buymeacoffee.com/fexingo

Lucas and Luna explore fuzz testing — why throwing random inputs at your code finds bugs that hand-written test cases never will. They trace the technique from its origins in the 1988 'finger' vulnerability through Google's OSS-Fuzz, which has found over 30,000 bugs in critical open-source projects. They discuss how a single fuzzing harness at Microsoft caught a decade-old bug in their Windows TCP/IP stack, and why modern CI pipelines can run fuzzers alongside unit tests without significant overhead. Luna challenges whether fuzzing is practical for early-stage startups; Lucas makes the case that even a simple 50-line fuzzer beats manual edge-case hunting. The episode closes on the question of whether fuzzing will become a regulatory requirement for safety-critical software.

#Fuzzing #FuzzTesting #SoftwareTesting #QA #Automation #EdgeCases #GoogleOSS-Fuzz #Microsoft #SecurityTesting #CI #DevOps #OpenSource #BugDetection #Tech #Technology #FexingoBusiness #BusinessPodcast #TestingPodcast

Keep every episode free: buymeacoffee.com/fexingo

Lucas and Luna dive into the quiet crisis of flaky test failures caused by unversioned test data. They break down how a single team at Shopify reduced CI retries by 40 percent by treating test fixtures like source code — with Git LFS, checksums, and data snapshots. Along the way, they discuss why randomized data generation is a trap, how database seeding scripts rot, and the one tool (Keploy) that auto-captures production traffic for replay. If you've ever re-run a test suite three times hoping it passes, this episode names the real culprit — and the fix.

#TestDataVersioning #FlakyTests #CIReliability #Shopify #GitLFS #Keploy #DataSnapshots #DatabaseSeeding #TestFixtures #QA #Automation #SoftwareEngineering #ContinuousIntegration #DevOps #Technology #FexingoBusiness #BusinessPodcast #SoftwareTestingWithFexingo

Keep every episode free: buymeacoffee.com/fexingo