Unlock The Power Of Property-Based Testing
summary
Claims that property-based testing generates many inputs to catch bugs that handcrafted examples miss and reduces maintenance by shrinking failures to minimal cases. Uses Clojure examples with custom email and integer generators, requests 1,000 examples but observes a failure after 15 and finds a minimal failing input via generators and shrinking that reveals a name truncation bug (code limited to 10 chars) which is fixed. Notes performance tradeoffs — roughly 200 ms for 10,000 iterations.
AI-written summary · about
chapters (15)
- 0:00Property-based testing intro
- 1:05Example-based tests limits
- 3:12Manual test limits
- 5:40Moving to property-based
- 7:47Realistic example
- 9:37Auto test inputs
- 10:19Understanding generators in depth
- 12:47Failure analysis
- 14:12Debug smallest failure
- 15:36Extending tests across stack
- 15:58Why shrinking matters
- 16:42PB testing challenges
- 17:25Time and complexity
- 18:06Tooling and language support
- 19:09Conclusion and key takeaways
related talks
54mAn Introduction to Property-based Testing
45mProperty based tests for the masses
27mAn introduction to property based testing
23mProperty based testing is a mindset
26mThe missing piece of testing
58mProperty Based Testing: Concepts and Examples
01h 24mIntroduction to Property Based Testing
30mProperty Based Testing: From Theory to Practice