BDD With Cucumber
summary
Argues that Cucumber is for BDD and readable specifications not a unit test tool, and that Gherkin scenarios serve as a single source of truth and executable docs. Uses Cucumber + Gherkin (demo in Malay), runs scenarios in Jenkins as CI regression, and keeps step definitions, hooks and helpers; notes maintenance pain from conventions and step explosion, and that some checks move into RSpec or Capybara. Mentions Cucumber supports 60 languages and the company’s CDN spans 170+ locations; the setup works for documentation and regression but requires strict conventions.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 2:20What is BDD
- 4:30BDD Tactics
- 6:37Recap
- 10:50Voting
- 13:40Cucumber
- 21:31How to use Cucumber
- 23:46My experience with Cucumber
- 25:22Documentation and regression
- 27:30Why Cucumber
- 28:50Cucumber Demo
- 33:04Questions
related talks
16mBDD with cucumber.js
09m"Effective ways of using BDD concept for Testing"
35mCucumber: Automating the Requirements Language You Already Speak
42mBDD Tests: Have Your End-to-End Tests Written for You
08m"BDD: NOT The Given-When-Then Thing"
40mHow Cucumber Can Improve Your Testing
45mLet's talk about software behaviour (BDD)
50mMake BDD great again