Skip to content
How to Test Race Conditions in Concurrent Code episode artwork

Aug 8, 2026 11 min

How to Test Race Conditions in Concurrent Code

from Software Testing with Fexingo: QA, Automation, and Reliable Software Engineering Hosted by Fexingo

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 tests that force interleavings, and practical steps to integrate race detection into CI. If you've ever debugged a heisenbug, this episode is for you. #RaceConditions #ConcurrencyTesting #SoftwareTesting #QA #Automation #ThreadSanitizer #GoRaceDetector #PropertyBasedTesting #Heisenbug #Fintech #CI #Tech #Business #FexingoBusiness #BusinessPodcast #SoftwareEngineering #DevOps #Testing Keep every episode free: buymeacoffee.com/fexingo

Episode details come from the podcast's RSS feed.

Embed this episode

Ready to play

How to Test Race Conditions in Concurrent Code

0:00 11:29

No transcript yet.

Requests help us decide what to transcribe next.

Frequently asked questions

How long is this episode of Software Testing with Fexingo: QA, Automation, and Reliable Software Engineering?

This episode is 11 minutes long.

When was this Software Testing with Fexingo: QA, Automation, and Reliable Software Engineering episode published?

This episode was published on August 8, 2026.

Can I download this Software Testing with Fexingo: QA, Automation, and Reliable Software Engineering episode?

Yes. Use the download control on the episode player to save the publisher-provided media file.