Domain Driven Testing: Know What You're Doing
summary
Applies Domain Driven Design to testing by making the domain concrete: ubiquitous language for naming, context map as test plan to focus tests, and approval testing to capture real production behavior. Recommends property based QuickTheories and JSON schema for invariant unit checks, snapshot and visual tools (BackstopJS, Applitools) for component approval, and task‑centric end to end tests via the screenplay pattern with Protractor or Rest Assured. Advises outsider exploratory blitzes, chaos monkey and data fuzzing, and setting an expiration date for architecture.
AI-written summary · about
chapters (10)
- 0:00Intro
- 0:33Goals
- 8:05Ubiquitous Language
- 14:27Context Map Example
- 19:02Design by Contract
- 24:05Team
- 26:24Expiration Date
- 31:57DDD Test Pyramid
- 38:42BackstopJS
- 42:51Protractor with Cucumber
related talks
42mDesign Driven Concepts for Automated Testing
33mHow to Practice Test Driven Development without Shooting Yourself in the Foot
43mBehavior Driven Development, or Agile 2.0
49mESSENTIALS - Canon Test-Driven Development
57mDomain Invariants & Property-Based Testing for the Masses
57mAdvanced Testing Techniques: Tips from the trenches
15mIntro to TDD and BDD
27mDomain Testing – Is It New or a Well-Forgotten Old?