Lucas and Luna dig into a specific case from May 2026: a major fintech app's checkout flow broke for screen-reader users after a seemingly harmless CSS update. They walk through how the bug slipped past unit and visual regression tests, why the team missed it, and what they changed to catch it next time. Luna brings data from WebAIM's 2025 screen-reader survey showing 67% of users encounter accessibility barriers monthly. Lucas explains the three-layer testing strategy the fintech team adopted: automated axe-core checks in CI, manual keyboard-only walkthroughs, and real screen-reader sessions on every release candidate. They also touch on the cost of ignoring accessibility — including a class-action lawsuit threat that got the company's attention. The episode ends with a practical takeaway: you don't need a dedicated accessibility team to start catching these bugs. A concrete number, one real company's mistake, and a fix any team can borrow.

#AccessibilityTesting #AxeCore #ScreenReader #WebAIM #Fintech #CSSBug #CheckoutFlow #CI #WCAG #DisabilityInTech #InclusiveDesign #ManualTesting #QA #SoftwareTesting #Technology #FexingoBusiness #BusinessPodcast #Episode33

Keep every episode free: buymeacoffee.com/fexingo

In this episode, Lucas and Luna dive into test prioritization — a smarter way to run test suites that cuts CI pipeline time without sacrificing quality. Lucas explains how techniques like risk-based sorting, historical failure data, and machine learning models can reduce test execution by 40 percent or more. They discuss real-world examples from Google's test automation research and how teams at companies like Spotify have implemented prioritization to speed up deployments. Luna asks about the trade-offs: does prioritization miss bugs that a full run would catch? Lucas walks through strategies like time-bucketed runs and smoke test layers to mitigate risk. If you've ever waited an hour for a CI pipeline to finish, this episode will give you concrete tactics to speed things up.

#TestPrioritization #CIPipeline #SoftwareTesting #ContinuousIntegration #TestAutomation #RiskBasedTesting #MachineLearning #RegressionTesting #SmokeTests #DevOps #QA #Technology #FexingoBusiness #BusinessPodcast #SoftwareEngineering #GoogleResearch #SpotifyEngineering #TestOptimization

Keep every episode free: buymeacoffee.com/fexingo

Episode 31 of Software Testing with Fexingo dives into load testing as a diagnostic tool for uncovering performance bugs that unit and integration tests miss. Lucas and Luna discuss how a simulated surge of 10,000 concurrent users on a fintech API exposed a memory leak that had been lurking for months, causing response times to degrade from 200ms to 8 seconds under peak load. They explain key concepts like ramp-up patterns, think time modeling, and the difference between load and stress testing. The hosts also explore how to set meaningful thresholds using the apdex score and why testing at 80 percent of expected peak can reveal database connection pool exhaustion. Practical advice includes using tools like k6 or Locust, integrating load tests into CI/CD pipelines, and the importance of testing with realistic data volumes. This episode helps QA engineers and developers build more resilient applications by catching performance regressions before they reach production.

#LoadTesting #PerformanceTesting #SoftwareTesting #QA #Automation #TechPodcast #FexingoBusiness #BusinessPodcast #SoftwareEngineering #DevOps #CI_CD #API #Fintech #MemoryLeak #Apdex #k6 #Locust #DatabasePerformance

Keep every episode free: buymeacoffee.com/fexingo

In episode 30 of Software Testing with Fexingo, Lucas and Luna explore how A/B testing can serve as a powerful bug-finding tool — catching issues in production before they impact all users. They walk through a real-world case from a major e-commerce platform that used controlled experiments to uncover a subtle regression in checkout flow, saving millions in lost revenue. The conversation covers setting up proper statistical thresholds, avoiding common pitfalls like novelty effects and sample ratio mismatch, and integrating A/B testing with traditional QA pipelines. By the end, listeners learn a practical framework for using experimentation not just for feature validation, but as a continuous safety net for software reliability.

#ABTesting #ExperimentalDesign #SoftwareTesting #QA #ReliabilityEngineering #RegressionTesting #ProductionTesting #StatisticalSignificance #FeatureFlags #ControlledExperiments #CheckoutFlow #Ecommerce #Tech #TestingStrategy #FexingoBusiness #BusinessPodcast #Technology #Podcast

Keep every episode free: buymeacoffee.com/fexingo

Lucas and Luna explore why testing on real devices is critical for catching hardware-specific bugs that emulators miss. They break down a case where a fintech app crashed on 4% of Android devices due to a GPU driver issue, discuss how Apple's silicon transition exposed emulator blind spots, and explain practical strategies like cloud-based device farms and targeted device matrices. This episode gives you concrete numbers and frameworks to improve your QA coverage.

#DeviceTesting #RealDevices #HardwareTesting #EmulatorLimitations #QA #SoftwareTesting #AndroidFragmentation #AppleSilicon #CloudDeviceFarm #Fintech #GPUBug #TestCoverage #BugReproduction #ContinuousTesting #TechPodcast #SoftwareEngineering #FexingoBusiness #BusinessPodcast

Keep every episode free: buymeacoffee.com/fexingo

In this episode of Software Testing with Fexingo, Lucas and Luna explore why many test automation efforts fail not because of bad tools, but because of missing feedback loops. They dive into a case study from a fintech startup that cut its bug-to-fix time by 70 percent by implementing a simple feedback mechanism: every failed test automatically created a structured bug report with logs, screenshots, and environment snapshots, then assigned it to the developer who last touched the affected code. The hosts discuss how this changes the psychology of test failures, the role of blameless post-mortems, and why feedback latency is the hidden metric every QA team should track. By the end, listeners understand why automation without feedback is just expensive noise, and how to build a system where tests teach teams, not just report red or green.

#TestAutomation #FeedbackLoop #QA #SoftwareTesting #BugTracking #DeveloperExperience #ContinuousIntegration #AutomationStrategy #FintechCaseStudy #BlamelessCulture #TestFailure #BugToFixTime #FeedbackLatency #EngineeringCulture #FexingoBusiness #BusinessPodcast #Technology #Podcast

Keep every episode free: buymeacoffee.com/fexingo

In this episode of Software Testing with Fexingo, Lucas and Luna explore why traditional end-to-end tests often miss critical failures—and how adding observability transforms them into powerful debugging tools. They walk through a real-world example: a major e-commerce checkout flow that passed all automated E2E tests but silently broke for users due to a third-party payment timeout. The hosts explain the 'test observability gap'—the disconnect between green test results and actual system health—and show how structured logging, distributed tracing, and metrics monitoring can catch the hidden bugs that flaky tests miss. Lucas shares a framework for instrumenting E2E tests with open-source tools like OpenTelemetry and custom health checks, while Luna challenges him on the cost and complexity trade-offs. They discuss a production incident at a mid-sized SaaS company where observability-tagged tests reduced mean time to detection from 4 hours to 12 minutes. By the end, listeners understand why a passing E2E test suite is no substitute for telemetry, and how to start bridging the gap today. The episode closes with a practical first step: adding a single trace to your most critical user journey.

#SoftwareTesting #EndToEndTesting #Observability #TestObservability #OpenTelemetry #DistributedTracing #Monitoring #DevOps #QATesting #TestAutomation #SaaS #Ecommerce #Debugging #FlakyTests #Technology #FexingoBusiness #BusinessPodcast #SoftwareEngineering

Keep every episode free: buymeacoffee.com/fexingo

In this episode of Software Testing with Fexingo, Lucas and Luna dive into the critical role of security testing in modern QA. While many teams focus on functional and performance testing, security testing often takes a back seat until a breach occurs. Lucas explains the key differences between penetration testing and automated vulnerability scanning, using the 2023 MOVEit Transfer vulnerability as a concrete example — a single SQL injection flaw that affected hundreds of organizations and cost billions in remediation. He highlights how integrating security testing into the CI/CD pipeline via dynamic analysis (DAST) and static analysis (SAST) can catch issues early, referencing a 2024 IBM study showing that fixing a vulnerability in production costs 30 times more than during design. Luna questions the practical barriers for small teams, and Lucas outlines a phased approach: start with SAST, add DAST for critical paths, and run periodic red-team exercises. The episode also touches on the importance of security culture through 'security champions' and the rising adoption of bug bounty programs. Listeners will walk away with a concrete roadmap for layering security testing without overwhelming their QA process.

#SecurityTesting #DevSecOps #SAST #DAST #PenetrationTesting #VulnerabilityScanning #MOVEitTransfer #SQLInjection #IBMSecurity #BugBounty #CICDPipeline #RedTeaming #ThreatModeling #OWASP #SoftwareTesting #Technology #FexingoBusiness #BusinessPodcast

Keep every episode free: buymeacoffee.com/fexingo

Lucas and Luna explore why traditional test pass/fail results aren't enough. They break down how observability-driven testing — combining structured logs, distributed traces, and real-time metrics — helps teams pinpoint root causes in minutes instead of hours. Using a real example from a fintech startup that cut its average debug time from 90 minutes to 15, they show how instrumenting your test suite with dashboards and alerts transforms QA from a bottleneck into a speed enabler. Plus: why the best debugging tool is the one you never have to open.

#TestObservability #Debugging #QA #SoftwareTesting #Observability #TestAutomation #RootCauseAnalysis #Fintech #Dashboards #StructuredLogging #DistributedTracing #RealTimeMetrics #ShiftLeft #TechPodcast #SoftwareEngineering #FexingoBusiness #BusinessPodcast #Technology

Keep every episode free: buymeacoffee.com/fexingo

Episode 24 of Software Testing with Fexingo dives into the overlooked power of logging. Lucas and Luna explore how structured logging, log levels, and observability pipelines can slash debugging time by up to 40 percent, using real-world examples like a production outage at a major e-commerce platform. They contrast logging with traditional debugging methods, discuss the ELK stack, and explain why semantic logging beats ad-hoc print statements. The episode ties back to test reliability—showing how logs complement automated tests to catch race conditions and transient failures. Perfect for QA engineers and developers tired of chasing ghosts in production.

#StructuredLogging #Debugging #Observability #ELKStack #LogLevels #ProductionDebugging #SoftwareTesting #QAEngineering #ReliabilityEngineering #LogAnalysis #SemanticLogging #RaceConditions #FlakyTests #IncidentResponse #Technology #FexingoBusiness #BusinessPodcast #SoftwareEngineering

Keep every episode free: buymeacoffee.com/fexingo