BDD in Action - Devoxx 2014

BDD in Action
John Ferguson Smart
Wakaleo Consulting
#DV14 #bddinaction @wakaleo

Miyamoto
Musashi
Japan
1584
–
1645

Consultant
Tr a i n e r
Mentor
Author
Speaker
Coder
John Fer guson Smar t

What
is
BDD
A
typical
BDD
workflow
What
tools
should
I
use?
Effec@ve
BDD
automa@on
BDD
Gotchas

So what is this BDD thing?
A
Test
Automa@on
Tool?

A
way
to
write
acceptance
criteria?

A
way
to
discover
requirements?

Using examples
a shared understanding
software that matters

Building the right software
Hunting out value Automated Acceptance
BDD
Criteria
API and code design
Collaboration
Living Documentation
Building the software right

The business owner
tells the business
analyst what he wants
1
BDD in a nutshell
2 The business
analyst writes a
requirements
document
3 The developer
translates the
requirements
into software
4 The tester
translates the
requirements
into test cases 5 The technical
writer translates
the software
into functional
and technical
documentation
A traditional development process

2
The business owner
and the business
analyst have a
conversation about
what he needs.
1
BDD in a nutshell
The scenarios guide the
developer and act as
automated tests
3
The business analyst,
the developer and the
tester elaborate the
requirements together.
They define
requirements as
structured, English-language
4 The tester uses
these scenarios
as the basis for
her tests
5
"scenarios"
The automated tests provide
feedback on progress and help
document the application
format
A BDD development process

2
The business owner
and the business
analyst have a
conversation about
what he needs.
1
The scenarios guide the
developer and act as
automated tests
3
The business analyst,
the developer and the
tester elaborate the
requirements together.
They define
requirements as
structured, English-language
4 The tester uses
these scenarios
as the basis for
•Specifica@ons
are
elaborated
collabora@vely
•Specifica@ons
use
her a
tests
common
language
•Executable
specifica@ons
provide
fast
feedback
5
"scenarios"
The automated tests provide
feedback on progress and help
document the application
format

Why bother with BDD?
•Focus
effort
•Reduce
waste
and
misaligned
requirements

Deliver
more
valuable
soMware

Make
changes
safely

Faster
and
more
reliable
releases

Reduced
maintenance
costs

Benefits of BDD
BDD
BDD
in
the
real
world
-‐
an
example

Adoption challenges
Demo
BDD
requires
high
business
engagement
and
collabora@on

Adoption challenges
Demo
BDD
works
best
in
an
Agile
or
Itera@ve
context

Adoption challenges
Demo
BDD
does
not
work
well
in
a
silo

Adoption challenges
Demo
Skill
and
prac@ce
required:
•Wri@ng
good
scenarios
takes
prac@ce
•Poorly
wriQen
tests
can
lead
to
higher
test-‐maintenance
costs
•Need
to
treat
test
automa@on
code
like
produc@on
code

BDD Gotchas
1
2
3
An@-‐paQern
1
The
business
analyst
writes
the
scenarios
4
and
then
gives
them
to
the
other
team
members.

1
2
3
BDD Gotchas
An@-‐paQern
2
4
The
tester
writes
the
scenarios
at
the
end
to
implement
an
automated
test
suite.

1
2
3
BDD Gotchas
An@-‐paQern
3
4
The
“Three
Amigos”
sessions
don’t
result
in
usable
scenarios,
so
the
developer
invents
them
a=erwards.
5

1
2
3
BDD Gotchas
An@-‐paQern
4
4
The
scenarios
are
too
UI-‐centric
or
detail-‐focused,
and
neglect
to
express
the
core
business
value.
5

BDD for high-level
requirements

Frequent Flyer Application
Goal: Encourage travellers to fly with Flying High airlines more often by allowing them to
cumulate Frequent Flyer points that they can spend on cheaper flights.
Goals
Earning points
from flights
Capabili9es
Earning points
from spending
with partners
Viewing points
earned
Spending points
on bookings
Viewing current points balance Features
View points needed to achieve
the next status level
Calculating points needed for
a given destination

Calculating points needed for a given destination
As a traveller
I want to know how many points I need to go to a given destination
So that I can plan my next trip with Flying High Airlines
Feature
Acceptance Criteria
-Need 2 points per km
-Members can calculate points needed on their account home page
Acceptance
Criteria
Automated
Acceptance
Criteria

Automated
Acceptance
Criteria
Automated
Acceptance
Tests

Automated
Acceptance
Tests
Applica9on
Code
Low
level
specifica9ons

A typical BDD workflow
“But
what
are
the
deliverables?
Meaningful
feedback
on
what
requirements
have
(and
have
not)
been
delivered

An incremental approach
“But
what
are
the
deliverables?
Descrip9on
of
each
feature
with
an
example
of
how
it
behaves

“But
what
are
the
deliverables?
…complete
with
illustra9ons

“But
what
are
the
deliverables?
How
was
each
feature
tested?

“But
what
are
the
deliverables?
Documenta9on
about
what
you
plan
to
deliver
in
each
release

“But
what
are
the
deliverables?
Useful
low-‐level
technical
documenta9on
with
liRle
overhead

“But
what
are
the
deliverables?
…and
targeted
automated
regression
tests

Flying High Application Architecture
AngularJS SPA
Flights
Web Service
Accounts
Web Service
Routes
Web Service

Flying High Test Architecture
(aka Thucydides)

Demo

BDD for detailed coding

Business
Goal
Business
Goal
Business
Goal
“building the software right”
FFeFeaeatatuturureresess FFeEeaxatatumurrepesless
Low level
speLcoifiwc aletvioenl s
speLcoifiwc alteivoenls
specifications
Executable
specifications
We
can
automate
these
examples
in
the
form
of
“executable
specifica@ons”

Business
Goal
Business
Goal
Business
Goal
FFeFeaeatatuturureresess FFeEeaxatatumurrepesless
Low level
speLcoifiwc aletvioenl s
speLcoifiwc alteivoenls
specifications
Executable
specifications
spock
RSpec
Low level
specifications
Low level
specifications
Low level
specifications
Low level
specifications
Low level
specifications
We
use
low-‐level
BDD
or
TDD
tools
to
define
the
behavior
of
components,
classes
etc.

Acceptance
criteria
tell
us
what
we
need
to
build…

What
would
we
like
the
API
to
look
like?

Then
write
low-‐level
specifica@ons
for
the
code

These
low
level
specifica@ons
become
technical
documenta@on
for
your
APIs

What tool should I use?

Collaboration before Automation
“Having
the
conversaDon
is
more
important
than
recording
the
conversaDon
is
more
important
than
automaDng
the
conversaDon”
-‐
Liz
Keogh

Know your audience

High-level BDD
Reporting for non-developers
as well as developers
Communicate about features
that business owners will
understand and find
meaningful
Higher automation and
maintenance costs
…

+ Groovy

(Previously known as “Thucydides”)
Living documentation
Requirements reporting
Encourages good test
architecture
Good WebDriver integration
Works with other BDD tools

+

A
high-‐level
BDD
tool
should
Produce
business-‐readable
results
Fit
smoothly
into
your
build
pipeline
Integrate
with
your
development
infrastructure
Allow
developers
to
collaborate
with
testers
to
implement
and
refactor
the
automa9on
code

Tips
for
more
effec@ve
BDD
Test
Automa@on

Tip #1 - Use Layers
Business
Rules
Business
Flow
Page/Component
interac9ons
Page/Component
details

Tip #2 - Favour non-UI tests where possible

Tip #3 - Know when not to automate
This slide is left intentionally blank

Low-level BDD
Technical documentation for
other developers
Implementation details that
business owners may not be
interested in
Faster to write and easier to
maintain
spock
RSpec

Low-level BDD
Good
naming
conven9ons
are
the
first
step
towards
BDD

Low-level BDD
spock
RSpec
Readable
executable
specifica9ons
in
Groovy

Low-level BDD
spock
RSpec
Great
support
for
data-‐driven
tests

Low-level BDD
spock
RSpec
Powerful
and
light-‐weight
stubbing
and
mocking

Low-level BDD
spock
RSpec
Makes
very
readable
specifica9ons

Low-level BDD
Lambda-Behave
Low-‐level
BDD
library
for
Java
8

Low-level BDD
Lambda-Behave
Data-‐driven
specifica9ons

Low-level BDD
Lambda-Behave
Generated
test
data

A
low-‐level
BDD
tool
should
Be
highly
readable
Be
developer-‐friendly
Make
it
easy
to
think
in
terms
of
specifica9ons,
not
tests
Encourage
fast
feedback
cycles
You
may
need
several!

There’s
more
where
this
came
from!
http://jbehave.org/
http://serenitybdd.com
https://code.google.com/p/spock/

There’s
more
where
this
came
from!
And
look
for
more
material
on
parleys.com!

Thank You

BDD in Action - Devoxx 2014

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Was ist angesagt?

Was ist angesagt? (20)

Andere mochten auch

Andere mochten auch (18)

Ähnlich wie BDD in Action - Devoxx 2014

Ähnlich wie BDD in Action - Devoxx 2014 (20)

Mehr von John Ferguson Smart Limited

Mehr von John Ferguson Smart Limited (12)

Kürzlich hochgeladen

Kürzlich hochgeladen (20)

BDD in Action - Devoxx 2014