Stop Testing, Start Storytelling
summary
Argues for writing tests as human stories that describe user-visible behavior rather than implementation details, using Rails and RSpec idioms like red green refactor and behavior‑driven expectations to program to interfaces. Cites real systems (Rails app with React front end and Go services) and a traffic case of hundreds of thousands of users in five minutes. Demonstrates an attempted live pseudo‑RSpec demo that lacks a volunteer, and prescribes a pendulum workflow: write the story, implement, return to the tests.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 0:47Agenda
- 5:43Goals for you
- 6:52What is testing
- 7:49Test Last
- 11:15TestFirst
- 11:51BehaviorDriven
- 13:15Stop Testing Start Storytelling
- 15:07What is Storytelling
- 15:57What is Communication
- 18:39What is Context
- 19:16Why Context Matters
- 21:42When We Can Tell Stories
- 23:02ObjectOriented Programming
- 23:24Built in Rails
- 26:48Encapsulation
- 30:59Conclusion
- 32:02Experiment
- 33:40Recap
- 37:25Action Plan
related talks
52mStory Driven Development: The Next Generation of Rails Functional Testing
01h 00mBehaviour Driven Development with RSpec
29mHow I Learned to Stop Worrying and Love Unit Testing
36mUsing Tests as a Tool to Wrangle Legacy Projects
27mThe TDD Treasure Map
37mSensible Testing
47mTelling Better Stories with Tests
29m"Testing. Why so serious?"