"BDD relies on the use of a very specific (and small) vocabulary to minimise miscommunication and to ensure that everyone – the business, developers, testers, analysts and managers – are not only on the same page but using the same words." Behavior Driven Development Wiki
User Stories or "Features" are expressed in the form:
In order to ....... |
(desired benefit or goal) |
....... should be able to |
(user role) |
............... |
(task, activity) |
"Features" are supported by conditions of satisfaction/acceptance criteria called "Scenarios", in the form:
Given that .......... |
(build) |
When ........... |
(operate) |
Then .......... |
(check) |