Balancing Early Testing with Real-World Reliability
summary
Argues that five concrete quality anchors map to SDLC stages and must be enforced: risk‑based acceptance criteria at define, heavy unit tests and contract tests in CI, isolated system regression in CD, and integrated stress checks before connection. Uses real failures: bridge pillar protection omitted, Mariner 1 lost for a missing averaging overbar, Mars Climate Orbiter metric/imperial mismatch, Knight Capital losing $440M in 45 minutes from a legacy flag, and Toyota fail‑safe failure under stress.
AI-written summary · about
chapters (17)
- 0:00Welcome
- 1:50Speaker introduction
- 3:14Testing fundamentals
- 4:17Unit and contract testing
- 6:45System and business correctness tests
- 8:11Testing and delivery lifecycle
- 9:16Four rings of defense
- 11:24Rings and testing pyramid
- 12:30Five quality anchors in SDLC
- 14:38Quality anchors examples
- 15:23Francis Scott Key Bridge collapse
- 17:32NASA Mariner 1 failure
- 20:24NASA Mars Climate Orbiter loss
- 23:22Knight Capital disaster
- 26:57Toyota unintended acceleration
- 29:08Summary of testing strategies
- 29:51Q&A on early testing
related talks
28mOrganizational Stability through Reliable Software through Testing
15mImprove continuous delivery by target quality aspects by your tests
26mPreventing disaster with data testing: Real-life examples and best practices
24mThe more we test, the worse?
57mAdvanced Testing Techniques: Tips from the trenches
22mTest Automation and Beyond: Implementing Continuous Testing Effectively
50mThe End of Testing as We Know It
01h 02mThe Art & Joy of Testing in Production