Why do we need to test?
summary
Claims four concrete values: reducing the feedback loop, trust, architecture, documentation. Tests cut the time between change and verification, but hot module reload and Storybook narrow that gap so testing’s other benefits matter more. Tests provide confidence that unmodified behavior remains intact, force components to become testable (and therefore smaller and better designed), and act as executable docs that stay correct if run on every change. Mentions TDD hesitation and Cypress component testing (Cypress 10).
AI-written summary · about
chapters (9)
- 0:00Start
- 0:09Why do we even test?
- 0:44TDD
- 1:23How do you think about testing?
- 2:57Value 1: Reducing the feedback loop
- 3:54Value 2: Trust
- 4:19Value 3: Architecture
- 5:09Value 4: Documentation
- 5:45Summary
related talks
01h 05mMicrotesting
24mTesting Less, Achieving More: How we mastered The Art of Strategic Testing
34mesting in modern times: A story about quality and value
11mNeed For Tests: Most Wanted
42mIntroducing the benefits of the testing diamond
21mTest Kitchen: A Recipe for Good Tests
48mTesting is Confidence - A Developer's Perspective
10mThe value of testing