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

How to Test Race Conditions in Concurrent Code
Concurrency bugs are among the hardest to catch—they hide in the space between threads, appearing only under specific timing. In this episode, Lucas and Luna explore how teams can systematically test race conditions using deterministic scheduling, stress testing, and static analysis. They dig into a real-world example: a fintech app that lost $40,000 to a race condition in a balance update, and how a combination of ThreadSanitizer, Go's race detector, and property-based testing caught it. The discussion covers why 'it works on my machine' fails for concurrency, how to design…
The skinny
The skinny isn't ready yet — notes appear once the transcript is processed.