Behavior Driven Development, or Agile 2.0
summary
Describes how Behavior Driven Development combines TDD, Domain-Driven Design and Scrum into executable requirements implemented with Java EE / Spring / Maven2, using JBehave and Selenium to convert user stories and example tables into automated specifications. Presents a layered testing strategy (unit, system, story) to avoid combinatorial explosion, and recommends Page Object patterns and gateway agents to isolate workflows from fragile UI selectors while treating specs as stable contracts.
AI-written summary · about
chapters (10)
- 0:00BDD introduction
- 3:32Waterfall vs Agile
- 8:12Scrum limitations
- 12:02User Story in BDD
- 17:02UI test automation issues
- 23:03Multi-level testing
- 30:37Unit, system, user story tests
- 35:12Declarative user stories
- 38:42User story specs
- 42:57BDD summary
related talks
41mBehavior-Driven Development: Feature this!
53mBehaviour Driven Development, BDD, with Cucumber for Java
01h 00mBehaviour Driven Development with RSpec
45mBehaviour Driven Development: Embrace Uncertainty
31mBDD: Behaviour Driven Development
45mBehaviour Driven Development and Behat: Telling Stories Through Code
38mHow Are We Supposed to Know what We Should Create?
48mMake Your Life Simple and Carefree with BDD