BDD in Action - Devoxx 2014

@wakaleo#DV14 #bddinaction

BDD in ActionJohn Ferguson Smart Wakaleo Consulting

Miyamoto Musashi Japan

1584 – 1645

John Ferguson Smart

Consultant Trainer Mentor Author Speaker Coder

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

A Test Automa@on Tool?

So what is this BDD thing?

A way to write acceptance criteria?

A way to discover requirements?

Using examples

a shared understanding

software that matters

Hunting out value Automated Acceptance Criteria

API and code design

Collaboration

Building the software right

Building the right software

Living Documentation

The business owner tells the business

analyst what he wants

12 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

BDD in a nutshell

A traditional development process

The business owner and the business

analyst have a conversation about

what he needs.

4 The tester uses these scenarios as the basis for

her tests

The automated tests provide feedback on progress and help

document the application

The business analyst, the developer and the tester elaborate the

requirements together.

The scenarios guide the developer and act as

automated tests

They define requirements as

structured, English-language format

"scenarios"

BDD in a nutshell

A BDD development process

The business owner and the business

analyst have a conversation about

what he needs.

4 The tester uses these scenarios as the basis for

her tests

The automated tests provide feedback on progress and help

document the application

The business analyst, the developer and the tester elaborate the

requirements together.

The scenarios guide the developer and act as

automated tests

They define requirements as

structured, English-language format

"scenarios"

•Specifica@ons are elaborated collabora@vely •Specifica@ons use a common language •Executable specifica@ons provide fast feedback

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 in the real world -‐ an example

BDD requires high business engagement and collabora@on

Adoption challenges

BDD works best in an Agile or Itera@ve context

Adoption challenges

BDD does not work well in a silo

Adoption challenges

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

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

BDD Gotchas

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

BDD Gotchas

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

BDD Gotchas

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

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.

Earning points from flights

Capabili9es

Earning points from spending with partners

Viewing points earned

Spending points on bookings

FeaturesViewing current points balance

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

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

…complete with illustra9ons

How was each feature tested?

Documenta9on about what you plan to deliver in each release

Useful low-‐level technical documenta9on with liRle overhead

An incremental approach

“But what are the deliverables?

…and targeted automated regression tests

AngularJS SPA

Flights Web Service

Accounts Web Service

Flying High Application Architecture

Routes Web Service

Flying High Test Architecture

(aka Thucydides)

BDD for detailed coding

Business Goal

We can automate these examples in the form of “executable specifica@ons”

FeaturesFeaturesFeatures FeaturesFeaturesExamplesLow level

specificationsLow level specificationsLow level specifications

Executable specifications

“building the software right”

Business Goal

We use low-‐level BDD or TDD tools to define the behavior of components, classes etc.

FeaturesFeaturesFeatures FeaturesFeaturesExamplesLow level

specificationsLow level specificationsLow level specifications

Executable specifications

spockRSpec

Low level specifications

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

Living documentationRequirements reportingEncourages good test architectureGood WebDriver integrationWorks with other BDD tools

(Previously known as “Thucydides”)

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

Business Rules

Business Flow

Page/Component interac9ons

Page/Component details

Tip #1 - Use Layers

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

spockRSpec

Low-level BDD

Good naming conven9ons are the first step towards BDD

Low-level BDD

spockRSpec

Readable executable specifica9ons in Groovy

Low-level BDD

spockRSpec

Great support for data-‐driven tests

Low-level BDD

spockRSpec

Powerful and light-‐weight stubbing and mocking

Low-level BDD

spockRSpec

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!

https://code.google.com/p/spock/

http://jbehave.org/

http://serenitybdd.com

There’s more where this came from!

And look for more material on parleys.com!

Thank You

BDD in Action - Devoxx 2014

Technology

Transcript of BDD in Action - Devoxx 2014

Devoxx devops university_2012

IzPack at Devoxx 2010

Pi4j Savage Devoxx

SparkSQL et Cassandra - Tool In Action Devoxx 2015

Vert.x devoxx london 2013

Retours Devoxx France 2016

Devoxx 2009 Conference session Jbpm4 In Action

BDD in Action – principles, practices and real-world application

Devoxx 2009 University session Jbpm4 In Action

Devoxx 2013 Summary/Keynotes

Devoxx 2014 Monitoring

Devoxx Booth Slide Loop

Activiti in Action (Devoxx 2010)

Devoxx enterprise scale angular

Devoxx UK Quickie 2015

Devoxx 2015 - BDD attention à la gueule de bois! 09-04-2015

JavaFX in Action (devoxx'16)

BDD in Action: Building Software Right and Building the Right Software

Devoxx 2014-webComponents

BDD in Action - Automated Web Testing with WebDriver and Serenity