~/talk

Design Driven Concepts for Automated Testing

links:none on file
slides:none on file

Argues that tests must drive component design rather than merely verify features, demonstrating a refrigerator drainage failure where a weak drain‑strap causes ice buildup and is fixed by a replacement part that works. Introduces contract tests that snapshot a known‑good interface and compare changes, collaboration tests that assert consumer‑observed behavior (including connection close under load), and integrity checks that run these at scale. Examples run in‑memory for fast feedback and a GitHub repo holds runnable samples.

AI-written summary · about

  1. 0:00Design driven testing concepts
  2. 2:53Water forms relevance
  3. 7:47Isolated testing failures
  4. 10:15Systems and interfaces
  5. 13:03Limits of end-to-end testing
  6. 17:14Design driven testing interfaces
  7. 22:36Contract and collaboration tests
  8. 25:44Design driven testing software
  9. 28:13How contract tests work
  10. 33:11Examples and GitHub repo
  11. 37:49Breaking down behaviors
  12. 39:12Legacy environment methodology
  13. 40:57Release pipeline impact
  14. 41:40Hexagonal architecture
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.