Behaviour Driven Development and Behat: Telling Stories Through Code
summary
Argues that BDD complements TDD by driving design with concrete examples and shows a working Behat workflow: write Gherkin features (PlayStation 4 basket examples, delivery rules), run tagged suites (domain / web UI / JavaScript) with Behat + Gherkin + Mink + Selenium, match steps to code via contexts, and inspect results — three scenarios passed (13 steps) in the demo and the JS browser check completes in 1.67 seconds, producing green tests and a maintainable separation of behavior and implementation.
AI-written summary · about
chapters (19)
- 0:00Start
- 1:44TDD ALONGSIDE BDD
- 3:31RIGHT THING
- 5:08WE'LL BE LOOKING AT SCENARIO BDD
- 7:30MULTIPLE STAKEHOLDERS
- 9:06CONVERSATIONS ARE KEY
- 10:13HAVE CONVERSATIONS BEFORE YOU START WRITING CODE
- 11:54EXAMPLES ARE ESSENTIAL
- 16:46KEYWORD BASED
- 17:01DOCUMENTATION
- 21:40SCENARIOS ARE EXAMPLES
- 21:57FEATURES CAN HAVE MULTIPLE SCENARIOS
- 25:35STORY STRUCTURE: THE MAKEUP OF A FEATURE FILE
- 26:01WRITING A GOOD STORY
- 30:32SUITES & PROFILES
- 31:05FOR EXAMPLE SUITES CAN USE THE SAME FEATURE FILES. OR SUITES CAN USE DIFFERENT FEATURE FILES
- 31:18WITH SUITES AND TAGS. YOU CAN USE THE SAME FEATURE FILE TO TEST DIFFERENT IMPLEMENTATIONS
- 32:37WITH SUITES AND TAGS YOU CAN CHANGE IMPLEMENTATION WITHOUT CHANGING YOUR DOCUMENTED BUSINESS RULES
- 43:11IN SUMMARY
related talks
26mBehaviour Driven Development with Laravel
31mBDD: Behaviour Driven Development
01h 00mBehaviour Driven Development with RSpec
17mUnlocking Collaboration in Code: A Journey through BDD
46mBehavior-Driven Development in Python
01h 04mDriving Design through Examples
45mBehaviour Driven Development: Embrace Uncertainty
48mBDD - It’s More Than Acceptance Tests