Domain Testing – Is It New or a Well-Forgotten Old?
summary
Describes domain testing as an algorithmic workflow (identify variables; define primary and secondary ranges; analyze dependencies to create tests; track untested variables) rather than a brand-new idea, tracing roots to Sam Kaner and ~2001. Shows a worked example (adding two two-digit numbers) using tables of test values, equivalence classes and boundary values across ~16 procedural steps and multi‑page tables, and discusses practical use: risk‑based test selection and where the method finds or misses bugs.
AI-written summary · about
chapters (14)
- 0:00Domain testing intro
- 1:38What is test design
- 3:22Definition and history
- 5:09Equivalence classes and boundaries
- 7:19Domain testing steps
- 10:34Practical example
- 12:45Variable analysis
- 15:18Primary and secondary ranges
- 17:39Test tables
- 19:58Variable dependencies
- 21:24Testing dependent variables
- 22:52Error assumptions and techniques
- 24:18Future of test design
- 25:45Test design mindset
related talks
54mDomain Driven Testing: Know What You're Doing
57mDomain Invariants & Property-Based Testing for the Masses
38mEquivalence Partitioning & Boundary Value Analysis: Old Hat or Cutting Edge?
53mTesting without dogma
39mAccess Points for Testing: From Human Opportunities to Digital Techniques
15mA Deep Dive into Data & Variables in Software Testing
01h 00mIs Testing Like Electricity?
51mAutomating to augment testing