BDD is a development approach derived from TDD that focuses on writing and automating tests of how functionality should work before coding. It aims to address issues with TDD such as where to start, what to test, and why tests fail. Tests should be written as sentences or scenarios using terms like "should" rather than "test". When a test fails, it indicates either broken code that needs fixing, a changed behavior that needs updating tests for, or an unnecessary behavior that can be deleted. BDD templates like scenarios describe user stories in a given-when-then format to define acceptance criteria. Tools like JBehave support automating BDD scenarios.

1. BDD- Behavior-driven development

2. History
• Author : Dan North
• First appeared in 2003
• Derived from TDD

3. TDD Issues
• Where to start
• What to test
• What not to test
• How much to test
• What to call the test
• Why a test failed

4. Test Names - agiledox
• Should be sentences
• Before:
– testIsASingleton
– testAReallyLongNameIsA
GoodThing
• After:
• is a singleton
• a really long name is a
good thing

5. Test Names - Should
• “Behaviour” is a more
useful word than “test”
• Start with should
• Target Class:TyreBuilder
Tests
 testShouldInflate - OK
 testShouldAccelerate - FAIL

6. When a test fails
1. You broke it – FIX it
2. The behavior was moved
somewhere else - Move the test
as well
3. The behavior changed - Don´t
be afraid of deleting it.

7. BDD is also “ubiquitous”
Scenarios Template
As a [X]
I want [Y]
so that [Z]
“A story’s behaviour is
simply its acceptance
criteria. So we created a
template to capture a
story’s acceptance
criteria.”

8. JBehave
Scenarios Template
Given : x with value 2
When : I divide by 2
Then : x should equal 1

9. JBehave

10. JBehave

11. Thanks
• QUESTIONS?
http://www.linkedin.com/in/diegomendonca