Spec Your Vibe with TDD
summary
Adds a user‑feedback flow to the default Flutter counter app that sends messages to Slack, switches from a webhook to the Slack API, and refactors UI state into a notifier plus a persistent feedback hub. Uses OpenSpec with Gherkin scenarios, a task checklist, and sub‑agent reviews; bot first creates failing scaffolding then produces 13 end-to-end tests that run against a fake network adapter and UI snapshot goldens. Enforces red–green TDD so tests exist before full implementation and must pass before moving on.
AI-written summary · about
chapters (13)
- 0:00Welcome
- 1:06Counter app case study
- 3:51First vibe-coded solution
- 5:42Guided bot questions
- 9:13Vibe coding to spec-driven
- 10:58Lessons from experiments
- 12:23OpenSpec development
- 15:55Customizing OpenSpec for test-driven development
- 18:45End-to-end tests first
- 22:16Red-green TDD guardrails
- 24:44Implementation review
- 26:09Key takeaways
- 27:36Q&A
related talks
41mThe art of Flutter testing
38mFlipping the Testing Pyramid
55mTurn specs into high quality apps
54mTDD Workshop: Outward-in Development, Unit Tests, and Fixture Data
01h 13mTDD Revisited
28mTDD: When the thrill has gone
46mTowards Joyful Development
49mAngular Testing In TDD - Writing a Feature Guided By a Responsible Maniac