BDD To The Bone: Acceptance Testing with Behave and Selenium
summary
Shows that natural-language requirements become runnable tests by mapping Gherkin to Python with behave and driving real browsers via selenium WebDriver Chrome, using plain asserts and a shared context to pass data between steps. Builds a tiny link shortener, runs executable specifications that open Chrome windows and confirm redirects, emits JUnit reports, and demonstrates passing and failing steps. Argues acceptance tests validate behavior not just code, and recommends embedding concrete numbers (eg 200 ms) for testable requirements.
AI-written summary · about
chapters (13)
- 0:00Requirements communication issues
- 2:50Gherkin for executable specs
- 5:00Gherkin to Behave mapping
- 7:30Solving requirements with Behave
- 10:00Acceptance vs developer testing
- 12:26Testing triangle value
- 13:28Making requirements testable
- 14:30Traceability with executable specs
- 15:55BDD as design methodology
- 16:36Acceptance testing Django
- 18:01Browser testing with Selenium
- 20:07Live demo Behave & Selenium
- 20:50Closing and key takeaways
related talks
46mBehavior-Driven Development in Python
09m"Effective ways of using BDD concept for Testing"
48mBDD - It’s More Than Acceptance Tests
45mBehaviour Driven Development and Behat: Telling Stories Through Code
29mBehavior-Driven Python
20mBDD: You’re doing it wrong!
54mTest automation with Python Behave without BDD
22mBDD (Behavior Driven Development) Testing for Django Apps