Cucumber: Automating the Requirements Language You Already Speak
summary
Claims that 50–56% of bugs stem from requirements and 45% of functionality is unused. Cucumber (Ruby) turns plain-English user stories into executable Gherkin scenarios stored in a features directory and backed by step definitions (regex → methods) that call Selenium/Watir/WebDriver, HTMLUnit or unit tests; use scenario outlines and tables for data-driven loops, tags and hooks for CI. Workflow is outside‑in: pending steps drive TDD down to code, green scenarios become living documentation; used successfully on web apps and APIs.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 1:02Requirements
- 2:50Acceptance Criteria
- 3:17Scenarios
- 4:20Workflow mentality
- 4:59Tables
- 6:19Background clauses
- 7:36User story
- 8:40Plain text files
- 9:11Regular expressions
- 11:25Other tools
- 13:19The overhead
- 14:13The user experience
- 14:47The outside in process
- 16:21Example business line
- 16:55Installing Cucumber
- 18:53Running Cucumber
- 21:46Acceptance Tests
- 23:10Testers
- 26:48Questions
related talks
36mBDD With Cucumber
40mHow Cucumber Can Improve Your Testing
16mBDD with cucumber.js
16mCucumber Tests: Legends and Reality
34mWriting end to end tests with a smile
37mCucumbers Have Layers: A Love Story
25mWriting end to end tests with a smile
41mLearning to speak a common language with BDD and pickled cucumbers