behaviour-driven development
Describe behavior through concrete examples shared by developers and domain experts.
Use this when Product rules are understood differently by different contributors.
without the term
“The product team and I keep disagreeing about how discounts work. Can you write out the rules as concrete examples, like given this cart when this happens then this price, and test against them?”
with the term · How do you ask a model for behaviour-driven development?
Write Given-When-Then scenarios for this rule. Include a boundary and a rejection, then verify the implementation against them.
What is behaviour-driven development?
Each rule becomes a scenario in plain language, often written as Given, When, Then, that a developer and a domain expert can both read and a test can run.
Why does behaviour-driven development matter when vibe coding?
A generated test may reproduce the code’s assumptions instead of the intended rule.
How do you do behaviour-driven development?
Choose examples with observable outcomes, including rejection and boundary cases.
What goes wrong with behaviour-driven development?
Treating scenario syntax alone as proof that the requirement is understood.