Equivalence Partitioning & Boundary Value Analysis: Old Hat or Cutting Edge?
summary
Claims that equivalence partitioning and boundary value analysis still cut test count dramatically by selecting one representative per partition and checking edges, backed by a worked example (days‑until‑Christmas program) that shows four partitions for a 1–100 integer range and boundaries 1 100 0 101, plus advice to use tables and domain testing techniques. Notes that industry underuses these methods, criticizes the three‑value BVA shortcut, and demonstrates the approach via simple tables that produce useful, actionable test cases.
AI-written summary · about
chapters (12)
- 0:00Intro
- 2:27Equivalence partitioning (EP)
- 7:21Examples of equivalence partitions
- 9:05Boundary value analysis (BVA)
- 17:05Domain testing
- 19:38Equivalence partitioning (step 1 - partition)
- 22:26Equivalence partitioning (step 2 - select)
- 28:03Different ways of partitioning one item
- 29:20Data item types (variables)
- 32:17Open boundaries
- 34:15Documentation and reuse
- 36:43Conclusions
related talks
27mDomain Testing – Is It New or a Well-Forgotten Old?
10m“Essential Mathematics for Testers”
48mDomain Invariants & Property-Based Testing for the Masses
28mYour Testing Strategy is broken - lets fix it!
22mThe Good, the Bad and the Ugly solutions in test design
18mValBench: Benchmarking exact value analysis
57mDomain Invariants & Property-Based Testing for the Masses
46mBoundaries