TDD Workshop: Outward-in Development, Unit Tests, and Fixture Data
summary
Live coding shows outward‑in TDD driving a to‑do feature: an RSpec+Capybara feature spec fails, test forces a new completions controller, nested route, migration adding a completed_at timestamp, and a link that posts to mark tasks complete; tests pass green, helpers extract page actions, duplication gets refactored, commits are squashed and pushed, and thoughtbot tools like RSPEC+Capybara and thoughtbot gems (FactoryGirl Shoulda Matchers mentioned) actually guide design and work.
AI-written summary · about
chapters (18)
- 0:00Intro
- 1:23Who are we
- 12:32Task Completion
- 13:09Task Naming
- 13:45Capybara DSL
- 17:32RSpec
- 19:28Let your errors drive what youre doing
- 21:19Think about the users flow upfront
- 22:53Task completions path
- 26:55Missing controller
- 31:32Completed at
- 35:23Fixed error
- 36:10Inspect spec features
- 38:16Commit history
- 42:53Integration tests
- 45:32Tests are still code
- 47:11Completing a task
- 50:36Push to master
