KEYNOTE: The Affordances of Quality
summary
Argues that quality depends on concrete affordances not slogans: a board with a separate QA column makes it trivially easy to “push quality later,” so remove the QA column; testability requires modular, observable, simple components so teams can mock dependencies and write fast unit tests, so design for testability; continuous delivery turns release from a two‑month manual merge and testing ordeal into a repeatable automated deploy (feature flags, CI that builds and tests on commit, a 20‑minute pipeline), so continuous delivery with 20‑minute pipeline.
AI-written summary · about
chapters (9)
- 0:00Welcome to TestCom Europe 2022
- 3:27Affordances in quality
- 10:54Mismatched affordances with Norman doors
- 15:31Board columns and quality affordances
- 21:50Testable systems as well-designed systems
- 32:32Continuous delivery for quality
- 44:57Fast and safe path
- 50:36Three key quality affordances
- 52:23Q&A
related talks
28mInstilling the built-in quality mindset into a dev team
53mNever-Neverland of pursuing Quality
49mIs your Quality on the Road to Nowhere?
28mQuality as an attitude – From Testing to Quality Engineering to…what?
14mThinking of Quality as developer productivity tool
35mWhy Software Engineers Should Make Quality a Priority
35mTesting != Quality
07m“Importance of Quality Assurance to a delivery team”