FIXING-UP PRODUCTION WITH PROPERTY-BASED TESTING
summary
Property-based testing plus targeted mocking and generator tuning reproduces a production sandbox corruption: increasing to 2000 samples and inspecting distributions yields a shrunk counterexample of 3 batches with empty options, revealing a swallowed-exception that skips the sandbox post‑condition; fixing the API to return error values removes the corruption. A followup failure is a Comparator contract violation that only appears on lists of 32 items (TimSort chunking); a tie‑breaker bug is fixed by returning zero for equal protein jobs.
AI-written summary · about
chapters (8)
- 0:00Start
- 1:09Property-based Testing for "Real"
- 2:37A Startup
- 3:40The Flow
- 4:39The Security Sub-system
- 6:15The Bug
- 7:09Unit tests
- 9:28Property-based Testing, Finally
related talks
26mThe missing piece of testing
20mUnlock The Power Of Property-Based Testing
51mProperty-Based Testing
54mAn Introduction to Property-based Testing
23mProperty based testing is a mindset
42mSurprise yourself with Property Based Testing
30mProperty Based Testing: From Theory to Practice
29mHardening Applications with Property Tests