~/talk

AssertTrue (isDecoupled(“my tests”))

slides:none on file

Argues that loose coupling cuts test maintenance: a quiz app change repeatedly breaks hundreds of UI-driven Selenium tests, tests sit skipped for months, and full suite runs take 30–40 minutes. Fix is layered testing: page objects and a DSL layer to shield UI churn, shift business checks to a service layer with adapters so external services become swappable, use email gateway spy storing messages and other test doubles to assert behavior, and create fixtures via object mother/test builders and in-memory repositories — this reduces failures and cuts runtime to seconds.

AI-written summary · about

  1. 0:00Start
  2. 9:25Test Parent
  3. 14:30Coupling Our Tests to the User Interface
  4. 19:03Domain-Specific Language Layer
  5. 28:56Testing Is Full of Compromises
  6. 35:43Is the Effort Required To Automate these Tests
  7. 37:20What Would Happen if We Replaced Our Entire Website with an Application with an App
  8. 1:02:03How Are You Using the Same Data across Tests
~/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.