Why Property-Based Testing Finds Bugs You Never Thought Of

Failed to add items

Sorry, we are unable to add the item because your shopping cart is already at capacity.

Add to basket failed.

Please try again later

Add to wishlist failed.

Please try again later

Remove from wishlist failed.

Please try again later

Adding to library failed

Please try again

Follow podcast failed

Unfollow podcast failed

Why Property-Based Testing Finds Bugs You Never Thought Of

Listen for free

View show details

In this episode of Software Testing with Fexingo, Lucas and Luna explore property-based testing, a technique that generates thousands of random inputs to find edge cases you'd never think to write as unit tests. They use a concrete example: a CSV parser that silently dropped rows with trailing spaces. With a Python library called Hypothesis, the team caught the bug in minutes after weeks of manual testing missed it. Lucas explains the difference between example-based and property-based testing, how to define invariants like 'every row has the same number of columns', and why this approach is especially powerful for data pipelines, APIs, and financial calculations. Luna pushes on the practical trade-offs — slower test runs, harder debugging — and they discuss when to use property-based tests versus traditional fuzzing. The episode ends with a reflection on how thinking in properties changes your mental model from 'does this work?' to 'what must always be true?'. #PropertyBasedTesting #Hypothesis #PythonTesting #CSVParsing #EdgeCases #SoftwareTesting #Automation #QA #DataPipelines #Invariants #Fuzzing #ExampleBasedTesting #TechPodcast #SoftwareEngineering #TestingTools #FexingoBusiness #BusinessPodcast #Technology Keep every episode free: buymeacoffee.com/fexingo

No reviews yet