In this episode, Lucas and Luna dive into contract testing—a strategy that catches integration bugs before they hit production. Using the real-world example of Netflix and its shift to microservices, they explain how consumer-driven contract tests (CDCs) act as a safety net for API changes. Lucas breaks down the difference between provider and consumer contracts, shares a concrete case where a mismatched field broke a payment pipeline, and discusses how tools like Pact and Spring Cloud Contract automate the process. Luna adds perspective on why contract testing beats end-to-end tests for speed and reliability, and how it fits into a CI/CD pipeline. They also touch on the trade-offs: maintenance overhead, cultural buy-in, and the risk of brittle contracts. Whether you're a QA engineer, a developer, or an architect, this episode gives you a practical framework for keeping distributed systems honest. June 25, 2026.

#ContractTesting #Microservices #Netflix #Pact #SpringCloudContract #API #CI/CD #ConsumerDrivenContracts #IntegrationTesting #SoftwareTesting #QA #Automation #TechPodcast #FexingoBusiness #BusinessPodcast #SoftwareEngineering #DevOps #TestingStrategy

Keep every episode free: buymeacoffee.com/fexingo

In this episode of Software Testing with Fexingo, Lucas and Luna dive into fuzz testing — a technique that bombards your software with unexpected, malformed, or random inputs to uncover security and stability bugs that traditional test cases miss. They break down how fuzzing works, why it's essential for input validation, and how a real-world example — a 2014 vulnerability in the Bash shell called Shellshock — could have been caught earlier with basic fuzzing. They also discuss practical ways to integrate fuzzing into your CI pipeline using tools like libFuzzer or OSS-Fuzz, and why even a few hundred test runs a day can surface hidden crashes. If you've ever wondered why your app fails on weird user input, this episode gives you a concrete strategy to find those bugs before your users do.

#Fuzzing #InputValidation #SoftwareTesting #QA #FuzzTesting #Shellshock #BashBug #LibFuzzer #OSSFuzz #CICD #SecurityTesting #CrashBugs #AutomatedTesting #TechPodcast #SoftwareEngineering #FexingoBusiness #BusinessPodcast #SoftwareTestingWithFexingo

Keep every episode free: buymeacoffee.com/fexingo

Lucas and Luna explore property-based testing, a technique where you define system invariants and let a tool generate thousands of random inputs to find edge cases hand-written tests overlook. They break down a real example from a financial transaction system where property-based tests caught a rounding bug that had survived for months. The episode covers the shift from example-based to property-based thinking, practical tools like Hypothesis for Python and QuickCheck for Java, and how teams can start small without rewriting their entire test suite. Lucas walks through a concrete property: 'for any valid trade, the sum of allocations equals the trade notional.' The hosts discuss common pitfalls like flaky properties and shrinking strategies that help debug failures. They also touch on the trade-off between property generality and test readability. The conversation ends with a forward look at how property-based testing fits into CI/CD pipelines and why it's gaining traction in fintech and safety-critical software.

#PropertyBasedTesting #SoftwareTesting #QA #Automation #Hypothesis #QuickCheck #TestAutomation #EdgeCases #Invariants #Fintech #TestingStrategy #Python #Java #BugDetection #Shrinking #CICD #FexingoBusiness #Technology

Keep every episode free: buymeacoffee.com/fexingo

In this episode of Software Testing with Fexingo, Lucas and Luna explore test impact analysis (TIA), a technique that uses code dependency mapping to determine exactly which tests need to run after a code change. They walk through how Google's CI system cut test execution time by 40% using TIA, and why most teams run far more tests than necessary. Lucas explains the difference between static and dynamic impact analysis, the role of build graphs, and how tools like Bazel and Nx implement this. Luna pushes back on adoption friction, and they discuss real-world results from a fintech startup that shaved 22 minutes off their CI pipeline. The episode closes with a reflection on shifting from coverage quantity to coverage efficiency — and a brief note on how listener support keeps the show ad-free.

#TestImpactAnalysis #RegressionTesting #SoftwareTesting #CI #Bazel #Nx #Google #BuildGraph #StaticAnalysis #DynamicAnalysis #CoverageEfficiency #DevOps #QA #Automation #Fintech #FexingoBusiness #BusinessPodcast #Technology

Keep every episode free: buymeacoffee.com/fexingo

In this episode of Software Testing with Fexingo, Lucas and Luna dive into log-based testing—a technique that uses your application's own logs to generate realistic test scenarios and catch silent failures. They explore a real case: how a major e-commerce platform discovered a catastrophic data corruption bug by replaying logs from a single user session. The discussion covers log parsing, anomaly detection, and why logs are an underutilized goldmine for QA. Lucas explains the difference between structured and unstructured logs, and Luna shares a cautionary tale about log bloat. By the end, you'll know how to turn your logging infrastructure into a continuous testing engine.

#LogBasedTesting #QA #SoftwareTesting #AnomalyDetection #LogParsing #StructuredLogging #TestData #ProductionMonitoring #SilentFailures #DataCorruption #ECommerce #UserSessionReplay #TestAutomation #Observability #TechPodcast #FexingoBusiness #BusinessPodcast #SoftwareEngineering

Keep every episode free: buymeacoffee.com/fexingo

Lucas and Luna dive into chaos engineering for APIs, exploring how Netflix's Chaos Monkey inspired a new wave of resilience testing for microservices. They break down a real case from a fintech startup that injected faults into their payment API to uncover hidden race conditions, saving them from a potential production outage during peak traffic. Learn how chaos testing differs from traditional stress tests, why it catches cascading failures that unit tests miss, and how you can start small with open-source tools like Chaos Toolkit without breaking your system. This episode covers the 'blast radius' concept, failure injection strategies, and why 2026's cloud-native architectures demand proactive chaos experiments. Perfect for QA engineers and developers looking to move beyond happy-path testing and build truly resilient APIs.

#ChaosEngineering #APITesting #ResilienceTesting #NetflixChaosMonkey #Microservices #FaultInjection #BlastRadius #ChaosToolkit #Fintech #QA #SoftwareTesting #Technology #FexingoBusiness #BusinessPodcast #APIs #RaceConditions #CloudNative #DevOps

Keep every episode free: buymeacoffee.com/fexingo

In this episode of Software Testing with Fexingo, Lucas and Luna dive into the hidden cost of flaky tests — tests that pass and fail without code changes. They break down a real-world case from a mid-size fintech company where flaky tests consumed 20% of developer time in a single quarter. They explore common causes like race conditions, async timeouts, and shared mutable state, then discuss practical strategies: quarantining flaky tests, using retry budgets, and investing in deterministic test environments. This is a must-listen for engineering teams trying to ship faster without losing confidence in their test suite. 8 minutes of actionable insight.

#FlakyTests #TestReliability #SoftwareTesting #QA #Automation #DeveloperProductivity #Fintech #RaceConditions #AsyncTesting #TestFlakiness #DeterministicTesting #RetryBudgets #TestQuarantine #Engineering #CI #Technology #FexingoBusiness #BusinessPodcast

Keep every episode free: buymeacoffee.com/fexingo

Lucas and Luna explore why pixel-perfect visual regression testing often fails to catch meaningful UI bugs, while perceptual diffing (like SSIM and DSSIM) catches the ones users actually see. They walk through a real case: an e-commerce checkout button whose hue shifted 3% — pixel tests flagged a false positive, then blind-spotted a real contrast failure. Engineers at a mid-size SaaS company reduced false alarms by 70% after switching to structural similarity indexing. The episode covers why 100% pixel match is the wrong target, how perceptual hashing works, and the trade-off between perceptual diffing and layout-aware assertions. Also: a brief, sincere mention of listener support at buy me a coffee dot com slash fexingo.

#VisualRegressionTesting #PerceptualDiffing #SSIM #DSSIM #UIQuality #PixelPerfect #FalsePositives #SoftwareTesting #QAAutomation #TestAutomation #FrontendTesting #EcommerceTesting #CheckoutFlow #UserExperience #RegressionTesting #Technology #FexingoBusiness #BusinessPodcast

Keep every episode free: buymeacoffee.com/fexingo

Episode 65 of Software Testing with Fexingo explores differential testing (a.k.a. metamorphic or diff testing) as a way to catch regressions when no oracle exists. Lucas explains how the technique works by comparing outputs of two program versions on the same input, using real-world examples like JPEG encoders. Luna pushes back on the cost of generating valid inputs and the challenge of flaky diffs. They discuss tools like AFL, LibFuzzer, and Cargo-diff, and when this method beats traditional unit or integration tests. The episode lands on a practical take: use diff testing for core algorithms where a simple transformation (re-encode, re-serialize) should yield identical results. No prior episode has covered this specific technique.

#DifferentialTesting #MetamorphicTesting #SoftwareTesting #RegressionTesting #QA #Automation #Fuzzing #LibFuzzer #AFL #CargoDiff #JPEGEncoders #TestOracle #FlakyTests #CoreAlgorithms #TechPodcast #FexingoBusiness #BusinessPodcast #Technology

Keep every episode free: buymeacoffee.com/fexingo

Episode 64 explores why paid crowdsourced testing platforms like uTest and Bugcrowd are finding defects that internal QA teams routinely overlook. Lucas and Luna break down a 2025 case study where a fintech app running on 15,000 real devices across 90 countries uncovered 47 unique edge-case bugs in two days — including a currency-format crash that only appeared on a Chinese Android build. They compare costs, turnaround times, and coverage gaps between in-house, outsourced, and crowdsourced testing, and explain when crowdsourcing makes sense vs. when it's overkill. If you've ever wondered whether your test matrix is too narrow, this episode gives you a concrete framework to evaluate the trade-offs.

#CrowdsourcedTesting #QA #EdgeCases #uTest #Bugcrowd #Fintech #DeviceCoverage #TestAutomation #SoftwareTesting #RealDeviceTesting #TestMatrix #BugBounty #MobileTesting #RegressionTesting #Technology #FexingoBusiness #BusinessPodcast #SoftwareEngineering

Keep every episode free: buymeacoffee.com/fexingo