Hardening Applications with Property Tests
summary
Property tests use Stream Data generators to validate Oban behaviors against Postgres under real concurrency, proving things like a CRON parser, unique jobs never duplicate under 2–5 concurrent inserters, and migration up/down correctness across 120 permutations. A single semi‑stateful property plus randomized actions runs ~100 variants and exposed failures that were fixed with advisory locks and transactional controls, leaving zero reported bugs aside from one namespacing issue and demonstrating one property test can replace brittle examples.
AI-written summary · about
chapters (10)
- 0:00Intro
- 2:00Streams
- 3:56What is Property Testing
- 4:58Property Test
- 7:40Handling Failures
- 9:34One Generator
- 10:16Unique Jobs
- 14:16Migrations
- 17:29Periodic Jobs
- 24:06QA Session
related talks
43mProperty-Based Testing - Examples from Business Applications
36mIntroduction to stateful property based testing
01h 24mIntroduction to Property Based Testing
23mProperty based testing is a mindset
58mProperty Based Testing: Concepts and Examples
51mProperty-Based Testing
20mUnlock The Power Of Property-Based Testing
41mProperty Based Testing with Hypothesis: Stronger Tests, Less Work