Hunting Bugs While Sleeping
summary
Explains property‑based testing with the Hypothesis library, replacing fixed examples by asserting algebraic properties (commutativity, double‑reverse) and generating randomized inputs; demo uses Hypothesis statistics showing 200 examples in a run (default 100) and shows how counterexamples surface failing input combinations. Shows a separate scheduled bug‑hunting CI pipeline in Azure DevOps and GitLab (daily or hourly) that runs many samples, lets you increase to 1000+ samples for CI, and reports failing cases so tests catch bugs while the team sleeps.
AI-written summary · about
chapters (13)
- 0:00Introduction and background
- 1:05What is property based testing
- 3:18Testing without expected output
- 5:30Exhaustive vs randomized inputs
- 7:20Why use a library like Hypothesis
- 8:24Advanced input criteria in testing
- 10:11When to use property based testing
- 11:18Automating bug hunting with CI
- 13:04Demo setup and integration
- 16:03Monitoring CI results
- 17:30Scheduling bug hunting CI
- 20:34Summary and resources
- 21:41Q&A session
related talks
27mTesting Beyond Examples: Property Based Testing with Hypothesis
50mProperty based testing with Hypothesis
32mMore testing with fewer tests
01h 07mSufficiently Advanced Testing
41mProperty Based Testing in Python with Hypothesis
41mProperty Based Testing with Hypothesis: Stronger Tests, Less Work
01h 31mIntroduction to Property-Based Testing
17mStop Writing Tests!
