Introduction to stateful property based testing
summary
Company uses PropEr style stateful property tests to model a key value patient DB and reproduces a PESEL bug that only appears for post‑2000 months, proving the model finds domain edge cases. Examples include AUTOSAR and LevelDB where a failing scenario shrinks to 16 operations and Dropbox ordering checks. Tests implement five callbacks, use guided generators, and rely on shrinking to produce minimal counterexamples. Upfront modeling cost is high but execution is fast unless shrinking repeats extensively.
AI-written summary · about
chapters (22)
- 0:00Intro
- 2:18Common examples
- 4:26Volvo Autostar
- 6:37LevelDB
- 7:39Dropbox
- 9:15Agenda
- 9:58List Reversal
- 11:12Oracle Properties
- 12:25Generators
- 14:36Managing state
- 15:52Stateful property based testing
- 17:48Example system
- 18:03Creating a model
- 18:45Implementing callbacks
- 19:39Handling searching
- 20:08Precondition postcondition answers
- 20:49Execution
- 23:04Guided execution
- 25:22Recap
- 26:26Conclusion
- 27:03Recommended book
- 27:37Questions
related talks
36mStateful property-based testing: with a game logic case study
23mProperty based testing is a mindset
46mProperty-based testing:You won't look at your tests the same way ever again
01h 24mIntroduction to Property Based Testing
51mProperty-Based Testing
58mProperty Based Testing: Concepts and Examples
01h 31mIntroduction to Property-Based Testing
36mProperty-Based Testing: Unveiling the Truth on Test Reduction