Declan Whelan, profile picture
Uploaded byDeclan Whelan
KEY, PPTX61,547 views

Specification by Example

The document discusses specification by example (SBE) as an approach to software development. It outlines key aspects of SBE including deriving scope from business goals, specifying collaboratively through examples, refining specifications, automating examples, and validating frequently through living documentation. An example is provided showing how SBE can be implemented using Cucumber features, steps, and system code.

Embed presentation

Download as KEY, PPTX
1 / 108
2 / 108
3 / 108
4 / 108
5 / 108
6 / 108
7 / 108
8 / 108
9 / 108
10 / 108
11 / 108
12 / 108
13 / 108
14 / 108
15 / 108
16 / 108
17 / 108
18 / 108
19 / 108
20 / 108
21 / 108
22 / 108
23 / 108
24 / 108
25 / 108
26 / 108
27 / 108
28 / 108
29 / 108
30 / 108
31 / 108
32 / 108
33 / 108
34 / 108
35 / 108
36 / 108
37 / 108
38 / 108
39 / 108
40 / 108
41 / 108
42 / 108
43 / 108
44 / 108
45 / 108
46 / 108
47 / 108
48 / 108
49 / 108
50 / 108
51 / 108
52 / 108
53 / 108
54 / 108
55 / 108
56 / 108
57 / 108
58 / 108
59 / 108
60 / 108
61 / 108
62 / 108
63 / 108
64 / 108
65 / 108
66 / 108
67 / 108
68 / 108
69 / 108
70 / 108
71 / 108
72 / 108
73 / 108
74 / 108
75 / 108
76 / 108
77 / 108
78 / 108
79 / 108
80 / 108
81 / 108
82 / 108
83 / 108
84 / 108
85 / 108
86 / 108
87 / 108
88 / 108
89 / 108
90 / 108
91 / 108
92 / 108
93 / 108
94 / 108
95 / 108
96 / 108
97 / 108
98 / 108
99 / 108
100 / 108
101 / 108
102 / 108
103 / 108
104 / 108
105 / 108
106 / 108
107 / 108
108 / 108
Specification By Example Declan Whelan @dwhelan
What’s the Problem?
Waterfall Source: http://www.cs.umd.edu/class/spring2003/cmsc838p/Process/waterfall.pdf
Waterfall X Source: http://www.cs.umd.edu/class/spring2003/cmsc838p/Process/waterfall.pdf
Cost Of Change Cost% Of% Change% Time%
Agile Specification Agile&Approach& Itera/on&1& Itera/on&2& Itera/on&3& Itera/on&4& Requirements& Requirements& Requirements& Requirements& Analysis&&&Design& Analysis&&&Design& Analysis&&&Design& Analysis&&&Design& Cost% of% Code& Code& Code& Code& Change% Test& Test& Test& Test& Deploy& Time%
Traditional Flow
Traditional Flow Specification
Traditional Flow Build Specification
Traditional Flow Build Specification Tests Cases
Traditional Flow Build Specification Test Tests Cases
Traditional Flow Build Specification Test Deploy Tests Cases
We Found a Bug! How did QA miss this? That was obvious! I shouldn't Developers don't test before have to spell out every they throw it over the wall! detail! Exec Tester Product Manager We did what was in functional spec! Business requirements weren't clear! BA missed it in the technical requirements! Dev BA Architect
We Found a Bug! How did QA miss this? That was obvious! I shouldn't Developers don't test before have to spell out every they throw it over the wall! detail! Exec Tester Product Manager We did what was in functional spec! Business requirements weren't clear! BA missed it in the technical requirements! Dev BA Architect
We Found a Bug! How did QA miss this? That was obvious! I shouldn't Developers don't test before have to spell out every they throw it over the wall! detail! Exec Tester Product Manager We did what was in functional spec! Business requirements weren't clear! BA missed it in the technical requirements! Dev BA Architect
We Found a Bug! How did QA miss this? That was obvious! I shouldn't Developers don't test before have to spell out every they throw it over the wall! detail! Exec Tester Product Manager We did what was in functional spec! Business requirements weren't clear! BA missed it in the technical requirements! Dev BA Architect
We Found a Bug! How did QA miss this? That was obvious! I shouldn't Developers don't test before have to spell out every they throw it over the wall! detail! Exec Tester Product Manager We did what was in functional spec! Business requirements weren't clear! BA missed it in the technical requirements! Dev BA Architect
We Found a Bug! How did QA miss this? That was obvious! I shouldn't Developers don't test before have to spell out every they throw it over the wall! detail! Exec Tester Product Manager We did what was in functional spec! Business requirements weren't clear! BA missed it in the technical requirements! Dev BA Architect
We Found a Bug! How did QA miss this? That was obvious! I shouldn't Developers don't test before have to spell out every they throw it over the wall! detail! Exec Tester Product Manager We did what was in functional spec! Business requirements weren't clear! BA missed it in the technical requirements! Dev BA Architect
Accidental Adversaries + Testing + New Bugs - + - + Testing Additional Development Software Fix Success Tests Success + - + - New Build + Development +
Functional Silos Source: http://www.danpontefract.com/images/silo.jpg
Functional Silos X Source: http://www.danpontefract.com/images/silo.jpg
Build it Right Build the Right Thing Specification By Example Gojko Adzic, 2011 page 4
Build it Right Build the Right Thing Useless Crap Specification By Example Gojko Adzic, 2011 page 4
Build it Right Business Failure Build the Right Thing Useless Crap Specification By Example Gojko Adzic, 2011 page 4
Build it Right Business Failure Build the Right Thing Useless Crap Maintenance Nightmare Specification By Example Gojko Adzic, 2011 page 4
Build it Right Business Failure Business Success Build the Right Thing Useless Crap Maintenance Nightmare Specification By Example Gojko Adzic, 2011 page 4
Build it Right Business Failure Business Success Specification By Example Build the Right Thing Useless Crap Maintenance Nightmare Specification By Example Gojko Adzic, 2011 page 4
What are Specifications By Example?
What are Specifications By Example? • Thin slices of system behaviour • that deliver business value • described as concrete examples • that are potentially automatable • without translation • to create executable specifications • captured in live documentation.
Agile Testing Quadrants
Specification By Example
Specification By Example Business Goal
Specification By Example Business Goal Derive the scope Scope
Specification By Example Business Goal Derive the scope Scope Specify collaboratively Key Examples
Specification By Example Business Goal Derive the scope Scope Specify collaboratively Key Examples Refine the specification Specification With Examples
Specification By Example Business Goal Derive the scope Scope Specify collaboratively Key Examples Refine the specification Specification With Examples Automate literally Executable Specification
Specification By Example Business Goal Derive the scope Scope Specify collaboratively Key Examples Refine the specification Specification With Examples Automate literally Executable Specification Validate frequently Living Documentation
Specification By Example Business Goal Derive the scope Scope Shared Understanding Ubiquitous Language Specify collaboratively Key Examples Refine the specification Specification With Examples Automate literally Executable Specification Validate frequently Living Documentation
Source: https://docs.google.com/drawings/d/1cbfKq-KazcbMVCnRfih6zMSDBdtf90KviV7l2oxGyWM/edit Specification By Example Business Goal Derive the scope Scope Shared Understanding Ubiquitous Language Specify collaboratively Key Examples Refine the specification Specification With Examples Automate literally Executable Specification Validate frequently Living Documentation
Derive the Scope: Story Mapping Source: http://availagility.co.uk/wp-content/uploads/2008/10/user-story-mapping.png
Derive the Scope: User Stories
Derive the Scope: User Stories As a _______ I want to _______ So that _______
Derive the Scope: User Stories As a _______ I want to _______ So that _______ As a student I want to purchase used books online So that I can save money
Specify Collaboratively: Workshops
Specify Collaboratively: Workshops
Specify Collaboratively: Workshops • Hold regular product backlog workshops
Specify Collaboratively: Workshops • Hold regular product backlog workshops • Full team workshops - when starting
Specify Collaboratively: Workshops • Hold regular product backlog workshops • Full team workshops - when starting • Three amigo workshops: • One developer • One tester • One analyst
Specify Collaboratively: Key Examples
Specify Collaboratively: Key Examples Given _______ When _______ Then _______
Specify Collaboratively: Key Examples Given _______ When _______ Then _______ Given “War and Peace” is available as a used book for $2.99 When Susan selects book“War and Peace” Then “Buy used for $2.99” is displayed
Refining the Specification
Refining the Specification “Specifications with examples are acceptance tests” Gojko Adzic
Refining the Specification “Specifications with examples are acceptance tests” Gojko Adzic • Be precise and make sure spec is testable
Refining the Specification “Specifications with examples are acceptance tests” Gojko Adzic • Be precise and make sure spec is testable • Avoid “scripts” and “flows”
Refining the Specification “Specifications with examples are acceptance tests” Gojko Adzic • Be precise and make sure spec is testable • Avoid “scripts” and “flows” • Focus on business functionality not design
Refining the Specification “Specifications with examples are acceptance tests” Gojko Adzic • Be precise and make sure spec is testable • Avoid “scripts” and “flows” • Focus on business functionality not design • Avoid UI details
Refining the Specification “Specifications with examples are acceptance tests” Gojko Adzic • Be precise and make sure spec is testable • Avoid “scripts” and “flows” • Focus on business functionality not design • Avoid UI details • Avoid covering every possible combination
Refining the Specification: An Example Free Delivery Free delivery is offered to VIP customers once they purchase a certain number of books. Free delivery is not offered to regular customers or VIP customers buying anything other than books. Customer Type Cart Contents Delivery VIP 5 books Free, Standard VIP 4 books Standard Regular 10 books Standard VIP 5 dishwashers Standard VIP 5 books, 1 dishwasher Standard Source: Specification by Example: How successful teams deliver the right software, Gojko Adzic, pg. 116
Automating Examples
Automating Examples • Start small
Automating Examples • Start small • Select important examples for automation
Automating Examples • Start small • Select important examples for automation • Plan up-front to automate
Automating Examples • Start small • Select important examples for automation • Plan up-front to automate • Be prepared to go slower at the start
Automating Examples • Start small • Select important examples for automation • Plan up-front to automate • Be prepared to go slower at the start • Treat automation code as a first class citizen
Automating Examples • Start small • Select important examples for automation • Plan up-front to automate • Be prepared to go slower at the start • Treat automation code as a first class citizen • Avoid record and playback
Automating Examples • Start small • Select important examples for automation • Plan up-front to automate • Be prepared to go slower at the start • Treat automation code as a first class citizen • Avoid record and playback • Avoid using pre-populated data
Minimize Tests Through the UI
Automation Tools FitNesse Cucumber Concordian Green JBehave Twist Pepper Robot Text Test SpecFlow Framework
Validate Frequently
Validate Frequently • Start with a Continuous Integration system
Validate Frequently • Start with a Continuous Integration system • Set up a Continuous Deployment system
Validate Frequently • Start with a Continuous Integration system • Set up a Continuous Deployment system • Specify and test business logic separately from end-to-end flows
Validate Frequently • Start with a Continuous Integration system • Set up a Continuous Deployment system • Specify and test business logic separately from end-to-end flows • Organize tests along functional lines
Validate Frequently • Start with a Continuous Integration system • Set up a Continuous Deployment system • Specify and test business logic separately from end-to-end flows • Organize tests along functional lines • Run all test nightly
Validate Frequently • Start with a Continuous Integration system • Set up a Continuous Deployment system • Specify and test business logic separately from end-to-end flows • Organize tests along functional lines • Run all test nightly • Consider an iteration “test pack”
Living Documentation • Keep specifications short • Evolve a specification language and leverage in with “common fixtures” • Make documentation accessible - consider a wiki • Organize the documentation • Put specifications under version control
A Worked Example
Executable Specification
Cucumber Organization fixtures are common Features Step System
Cucumber Organization fixtures are common ad Lo Features Step System
Cucumber Organization fixtures are common M ad at Lo ch Features Step System
Cucumber Organization fixtures are common M ad at Lo ch Features Step Call System
Feature File Feature: Turn cucumber into beer As a cucumber presenter I want beer after my presentation So I can enjoy the rest of DemoCampGuelph Scenario: Brydon buys Declan beer Given Brydon hosts DemoCampGuelph When Declan demos Cucumber Then Brydon should buy Declan 1 beer Scenario: Ali buys Declan beer Given Ali hosts DemoCampGuelph When Declan demos Cucumber Then Ali should buy Declan 1 beer
Step Definitions Given /^(.+) hosts/ do |host| @event = Event.new(host) end When /^(.+) demos/ do |presenter| @event.add(presenter) end Then /^(.+) should buy (.+) (d+) (.*)$/ do |buyer, drinker, qty, item| perk = @event.perks[0]; perk.buyer.should == buyer; perk.receiver.should == drinker perk.quantity.should == quantity.to_i; perk.item.should == item end
System Under Test class Event attr_reader :perks def initialize(host) @host = host; @perks = [] end def add(presenter) @perks.push Perk.new(@host, presenter, 1, "beer") end end class Perk attr_reader :buyer, :receiver, :quantity, :item def initialize(buyer, receiver, quantity, item) @buyer = buyer; @receiver = receiver @quantity = quantity; @item = item end end
Execution Scenario: Brydon buys Declan beer Given Brydon hosts DemoCampGuelph When Declan demos Cucumber Then Brydon should buy Declan 1 beer
Execution Scenario: Brydon buys Declan beer Given Brydon hosts DemoCampGuelph When Declan demos Cucumber Then Brydon should buy Declan 1 beer Given /^(.+) hosts/ do | When /^(.+) demos/ do | host| presenter| @event = @event.add(presenter) Event.new(host) end End Then /^(.+) should buy (.+) (d+) (.*)$/ do |buyer, drinker, qty, item| perk = @event.perks[0]; perk.buyer.should == buyer; perk.receiver.should == drinker
Execution Scenario: Brydon buys Declan beer Given Brydon hosts DemoCampGuelph When Declan demos Cucumber Then Brydon should buy Declan 1 beer Given /^(.+) hosts/ do | host| @event = Event.new(host) End
Execution Scenario: Brydon buys Declan beer Given Brydon hosts DemoCampGuelph When Declan demos Cucumber Then Brydon should buy Declan 1 beer Given /^(.+) hosts/ do | host| “Brydon” @event = Event.new(host) End
Execution Scenario: Brydon buys Declan beer Given Brydon hosts DemoCampGuelph When Declan demos Cucumber Then Brydon should buy Declan 1 beer
Execution Scenario: Brydon buys Declan beer Given Brydon hosts DemoCampGuelph When Declan demos Cucumber Then Brydon should buy Declan 1 beer Given /^(.+) hosts/ do | When /^(.+) demos/ do | host| presenter| @event = @event.add(presenter) Event.new(host) end End Then /^(.+) should buy (.+) (d+) (.*)$/ do |buyer, drinker, qty, item| perk = @event.perks[0]; perk.buyer.should == buyer; perk.receiver.should == drinker
Execution Scenario: Brydon buys Declan beer Given Brydon hosts DemoCampGuelph When Declan demos Cucumber Then Brydon should buy Declan 1 beer When /^(.+) demos/ do | presenter| @event.add(presenter) end
Execution Scenario: Brydon buys Declan beer Given Brydon hosts DemoCampGuelph When Declan demos Cucumber Then Brydon should buy Declan 1 beer When /^(.+) demos/ do | presenter| @event.add(presenter) end “Declan”
Execution Scenario: Brydon buys Declan beer Given Brydon hosts DemoCampGuelph When Declan demos Cucumber Then Brydon should buy Declan 1 beer
Execution Scenario: Brydon buys Declan beer Given Brydon hosts DemoCampGuelph When Declan demos Cucumber Then Brydon should buy Declan 1 beer Given /^(.+) hosts/ do | When /^(.+) demos/ do | host| presenter| @event = @event.add(presenter) Event.new(host) end End Then /^(.+) should buy (.+) (d+) (.*)$/ do |buyer, drinker, qty, item| perk = @event.perks[0]; perk.buyer.should == buyer; perk.receiver.should == drinker
Execution Scenario: Brydon buys Declan beer Given Brydon hosts DemoCampGuelph When Declan demos Cucumber Then Brydon should buy Declan 1 beer Then /^(.+) should buy (.+) (d+) (.*)$/ do |buyer, drinker, qty, item| perk = @event.perks[0]; perk.buyer.should == buyer; perk.receiver.should == drinker
Execution Scenario: Brydon buys Declan beer Given Brydon hosts DemoCampGuelph When Declan demos Cucumber Then Brydon should buy Declan 1 beer Then /^(.+) should buy (.+) (d+) (.*)$/ do |buyer, drinker, qty, item| perk = @event.perks[0]; perk.buyer.should == buyer; perk.receiver.should == drinker
Source: https://docs.google.com/drawings/d/1cbfKq-KazcbMVCnRfih6zMSDBdtf90KviV7l2oxGyWM/edit Specification By Example Business Goal Derive the scope Scope Shared Understanding Ubiquitous Language Specify collaboratively Key Examples Refine the specification Specification With Examples Automate literally Executable Specification Validate frequently Living Documentation
Build it Right Build the Right Thing Specification By Example Gojko Adzic, 2011 page 4
Build it Right Build the Right Thing Useless Crap Specification By Example Gojko Adzic, 2011 page 4
Build it Right Business Failure Build the Right Thing Useless Crap Specification By Example Gojko Adzic, 2011 page 4
Build it Right Business Failure Build the Right Thing Useless Crap Maintenance Nightmare Specification By Example Gojko Adzic, 2011 page 4
Build it Right Business Failure Business Success Build the Right Thing Useless Crap Maintenance Nightmare Specification By Example Gojko Adzic, 2011 page 4
Build it Right Business Failure Business Success Specification By Example Build the Right Thing Useless Crap Maintenance Nightmare Specification By Example Gojko Adzic, 2011 page 4
Reading Specification By Example Gojko Adzic The RSpec Book: Behaviour Driven Development with RSpec, Cucumber and Friends David Cheliminksy et al Agile Testing: A Practical Guide for Testers and Agile Teams Lisa Crispin, Janet Gregory
Diagram Credits Lisa Crispin and Janet Gregory Agile Testing: A Practical Guide for Testers and Agile Teams Addison-Wesley Professional; January 9, 2009. Mike Cohn Succeeding with Agile: Software Development Using Scrum Addison-Wesley Professional; November 5, 2009.

More Related Content

PPTX
Agile-overview: Agile Manifesto, Agile principles and Agile Methodologies
byBalaji Sathram
 
PPTX
Specification by example
byAsier Barrenetxea
 
PDF
Successfully Implementing BDD in an Agile World
bySmartBear
 
PPTX
Behavior driven development (bdd)
byRohit Bisht
 
ODP
Introduction to BDD
byKnoldus Inc.
 
PDF
Scrum Meetings Infographic v12
byNigel Thurlow
 
PDF
An introduction to Behavior-Driven Development (BDD)
bySuman Guha
 
PPT
Definition Of Done
byWei Zhu
 
Agile-overview: Agile Manifesto, Agile principles and Agile Methodologies
byBalaji Sathram
 
Specification by example
byAsier Barrenetxea
 
Successfully Implementing BDD in an Agile World
bySmartBear
 
Behavior driven development (bdd)
byRohit Bisht
 
Introduction to BDD
byKnoldus Inc.
 
Scrum Meetings Infographic v12
byNigel Thurlow
 
An introduction to Behavior-Driven Development (BDD)
bySuman Guha
 
Definition Of Done
byWei Zhu
 

What's hot

PPTX
Sprint review presentation
byBernhardBoennemann
 
PPTX
How to Design a Successful Test Automation Strategy
byImpetus Technologies
 
PPT
Agile Metrics
byMikalai Alimenkou
 
PPTX
Strategies to split user stories
bycpolc
 
PPT
User Story Mapping (2008)
byJeff Patton
 
PDF
21 técnicas para quebra de User Stories para os PO's
byCarlos Silva Júnior
 
PPT
End to end testing - strategies
byanuvip
 
PDF
IIT Academy: 204 User stories and acceptance criteria
bySteven HK Ma ｜ 馬國豪
 
PPTX
Introduction to Bdd and cucumber
byNibu Baby
 
PDF
Cheat Sheet: 8 ways to split your user stories
byPayton Consulting
 
PDF
DevCamp - O papel de um testador em uma equipe ágil
byElias Nogueira
 
PPT
SMART Requirements
byHarmony Brenner, ISTQB (CTFL)
 
PPTX
Agile Release Planning
byAdnan Aziz
 
PPTX
BDD WITH CUCUMBER AND JAVA
bySrinivas Katakam
 
PPTX
Release Management: Successful Software Releases Start with a Plan
byconnielharper
 
PDF
An Introduction to Test Driven Development
byCodeOps Technologies LLP
 
PDF
Why Should we use Microsoft's Playwright
byKnoldus Inc.
 
PDF
Definition of Ready (XP2011)
byKen Power
 
PDF
Tutorial: Implementing Specification-By-Example with Gherkin
byChristian Hassa
 
PPSX
Cucumber & gherkin language
byselvanathankapilan
 
Sprint review presentation
byBernhardBoennemann
 
How to Design a Successful Test Automation Strategy
byImpetus Technologies
 
Agile Metrics
byMikalai Alimenkou
 
Strategies to split user stories
bycpolc
 
User Story Mapping (2008)
byJeff Patton
 
21 técnicas para quebra de User Stories para os PO's
byCarlos Silva Júnior
 
End to end testing - strategies
byanuvip
 
IIT Academy: 204 User stories and acceptance criteria
bySteven HK Ma ｜ 馬國豪
 
Introduction to Bdd and cucumber
byNibu Baby
 
Cheat Sheet: 8 ways to split your user stories
byPayton Consulting
 
DevCamp - O papel de um testador em uma equipe ágil
byElias Nogueira
 
SMART Requirements
byHarmony Brenner, ISTQB (CTFL)
 
Agile Release Planning
byAdnan Aziz
 
BDD WITH CUCUMBER AND JAVA
bySrinivas Katakam
 
Release Management: Successful Software Releases Start with a Plan
byconnielharper
 
An Introduction to Test Driven Development
byCodeOps Technologies LLP
 
Why Should we use Microsoft's Playwright
byKnoldus Inc.
 
Definition of Ready (XP2011)
byKen Power
 
Tutorial: Implementing Specification-By-Example with Gherkin
byChristian Hassa
 
Cucumber & gherkin language
byselvanathankapilan
 

Viewers also liked

PDF
Reinventing Software Quality, Agile Days Moscow 2013
bygojkoadzic
 
PDF
Time to Bet on the Cloud?
bygojkoadzic
 
ODP
5 key challenges
bygojkoadzic
 
PDF
Serverless Code Camp Barcelona
bygojkoadzic
 
ODP
Death to the testing phase
bygojkoadzic
 
PPT
Effective specifications for agile teams
bygojkoadzic
 
PPT
Challenging Requirements/Oredev
bygojkoadzic
 
PDF
Test Automation Without the Headache: Agile Tour Vienna 2015
bygojkoadzic
 
PDF
How I learned to stop worrying and love flexible scope - at JFokus 2014
bygojkoadzic
 
PDF
Serverless JavaScript
bygojkoadzic
 
PPTX
From Grid to Cloud
bygojkoadzic
 
PDF
Sabotage product
bygojkoadzic
 
PDF
Agile Testers: Becoming a key asset for your team
bygojkoadzic
 
PPT
Specification by example and agile acceptance testing
bygojkoadzic
 
Reinventing Software Quality, Agile Days Moscow 2013
bygojkoadzic
 
Time to Bet on the Cloud?
bygojkoadzic
 
5 key challenges
bygojkoadzic
 
Serverless Code Camp Barcelona
bygojkoadzic
 
Death to the testing phase
bygojkoadzic
 
Effective specifications for agile teams
bygojkoadzic
 
Challenging Requirements/Oredev
bygojkoadzic
 
Test Automation Without the Headache: Agile Tour Vienna 2015
bygojkoadzic
 
How I learned to stop worrying and love flexible scope - at JFokus 2014
bygojkoadzic
 
Serverless JavaScript
bygojkoadzic
 
From Grid to Cloud
bygojkoadzic
 
Sabotage product
bygojkoadzic
 
Agile Testers: Becoming a key asset for your team
bygojkoadzic
 
Specification by example and agile acceptance testing
bygojkoadzic
 

Similar to Specification by Example

PPT
Coding Standards
byJeevitesh Ms
 
PPTX
10 Reasons Your Software Sucks - Election 2012 Edition
byCaleb Jenkins
 
PDF
PL/SQL Development
byThanh Nguyen
 
PDF
ChannelStream: The challenges of continuously delivering
byjfitzell
 
PDF
The Challenge of Continuously Delivering
byESUG
 
PPTX
Microsoft Stack Visual Studio 2010 Overview
byrfennell
 
PDF
Testing for continuous delivery with visual studio 2012
byCristiano Caetano
 
PPTX
Development without Testers: Myth or Real Option? (ConfeT&QA conference)
byMikalai Alimenkou
 
PDF
Improving your SDLC
byJohn Ferguson Smart Limited
 
PPTX
Development without Testers: Myth or Real Option?
byMikalai Alimenkou
 
PDF
Technical debt
byLeanAgileTraining
 
PDF
Clean code and code smells
byMd. Aftab Uddin Kajal
 
PDF
ESEconf2011 - Buschmann Frank: "What architects need to know"
byAberla
 
PDF
Customers don't tell, YOU have to ask
bySTAG Software Private Limited
 
PDF
Achieving Zero Defect with Agile Methods BugDay Bangkok 2012 โดย Varokas Pan...
byPrathan Dansakulcharoenkit
 
PDF
Teaching and Learning TDD in the Coding Dojo
byEmily Bache
 
PPTX
Build Quality In
byKishen Simbhoedatpanday
 
PDF
Agile Software Development in Practice - A Developer Perspective
byWee Witthawaskul
 
PPTX
Session #1: Development Practices And The Microsoft Approach
bySteve Lange
 
PDF
The Future Tester at Suncorp - A Journey of Building Quality In Through Agile
byCraig Smith
 
Coding Standards
byJeevitesh Ms
 
10 Reasons Your Software Sucks - Election 2012 Edition
byCaleb Jenkins
 
PL/SQL Development
byThanh Nguyen
 
ChannelStream: The challenges of continuously delivering
byjfitzell
 
The Challenge of Continuously Delivering
byESUG
 
Microsoft Stack Visual Studio 2010 Overview
byrfennell
 
Testing for continuous delivery with visual studio 2012
byCristiano Caetano
 
Development without Testers: Myth or Real Option? (ConfeT&QA conference)
byMikalai Alimenkou
 
Improving your SDLC
byJohn Ferguson Smart Limited
 
Development without Testers: Myth or Real Option?
byMikalai Alimenkou
 
Technical debt
byLeanAgileTraining
 
Clean code and code smells
byMd. Aftab Uddin Kajal
 
ESEconf2011 - Buschmann Frank: "What architects need to know"
byAberla
 
Customers don't tell, YOU have to ask
bySTAG Software Private Limited
 
Achieving Zero Defect with Agile Methods BugDay Bangkok 2012 โดย Varokas Pan...
byPrathan Dansakulcharoenkit
 
Teaching and Learning TDD in the Coding Dojo
byEmily Bache
 
Build Quality In
byKishen Simbhoedatpanday
 
Agile Software Development in Practice - A Developer Perspective
byWee Witthawaskul
 
Session #1: Development Practices And The Microsoft Approach
bySteve Lange
 
The Future Tester at Suncorp - A Journey of Building Quality In Through Agile
byCraig Smith
 

More from Declan Whelan

PPTX
Technical debt is a systemic problem - not a personal failing
byDeclan Whelan
 
PPTX
From Technical Debt to Technical Health
byDeclan Whelan
 
PPTX
effective agile adoption
byDeclan Whelan
 
PPTX
Big Balls of Mud
byDeclan Whelan
 
PDF
Navigating Organizational Change
byDeclan Whelan
 
PPT
Simple Design
byDeclan Whelan
 
PDF
Domain Driven Design and Hexagonal Architecture with Rails
byDeclan Whelan
 
PPT
Win Win Conversations
byDeclan Whelan
 
PDF
Agile 2012 Simple Design Applied
byDeclan Whelan
 
PPTX
Releasing your teams energy through 'pull' conversations
byDeclan Whelan
 
KEY
Solid principles
byDeclan Whelan
 
PPTX
Learning is Key to Agile Success: Agile Vancouver 2010
byDeclan Whelan
 
PPTX
Agile learning agile 2010
byDeclan Whelan
 
PPTX
Agile Learning (60 minute version)
byDeclan Whelan
 
PPTX
Cuke2Beer
byDeclan Whelan
 
PPTX
Agile Learning from Agile 2009
byDeclan Whelan
 
PPTX
Agile, Tdd And .Net
byDeclan Whelan
 
PPTX
Agile Testing: The Role Of The Agile Tester
byDeclan Whelan
 
Technical debt is a systemic problem - not a personal failing
byDeclan Whelan
 
From Technical Debt to Technical Health
byDeclan Whelan
 
effective agile adoption
byDeclan Whelan
 
Big Balls of Mud
byDeclan Whelan
 
Navigating Organizational Change
byDeclan Whelan
 
Simple Design
byDeclan Whelan
 
Domain Driven Design and Hexagonal Architecture with Rails
byDeclan Whelan
 
Win Win Conversations
byDeclan Whelan
 
Agile 2012 Simple Design Applied
byDeclan Whelan
 
Releasing your teams energy through 'pull' conversations
byDeclan Whelan
 
Solid principles
byDeclan Whelan
 
Learning is Key to Agile Success: Agile Vancouver 2010
byDeclan Whelan
 
Agile learning agile 2010
byDeclan Whelan
 
Agile Learning (60 minute version)
byDeclan Whelan
 
Cuke2Beer
byDeclan Whelan
 
Agile Learning from Agile 2009
byDeclan Whelan
 
Agile, Tdd And .Net
byDeclan Whelan
 
Agile Testing: The Role Of The Agile Tester
byDeclan Whelan
 

Recently uploaded

PDF
Computer-Based Training (CBT) The Backbone of Modern Technical & Defence Trai...
bycomputerbasedtrainin1
 
PDF
ICT500 - CRITICAL AND CREATIVE THINKING FOR INFORMATION TECHNOLOGY SOLUTIONS:...
by2024432452
 
PDF
Build Next-Gen Spatial & Sensor Workflows: Secure, Scalable Processing in Sno...
bySafe Software
 
PDF
React Mastery: Visual Mental Models to Understand React Deeply
byThomas Gaye
 
PDF
Adapt.com Seed Fundraising Deck | The AI Computer for Business
byashley459565
 
PDF
Certified AI-Native Foundations Professional.pdf
byMarc Entsminger SPC6, RTE, SSM, SA, SDP
 
PDF
7 Essential Types of Penetration Testing Services Every Business Should Under...
bypandeydevika621
 
PPTX
Software Engineering in the Age of AI Agents
byHusseinMalikMammadli
 
PPTX
TechSprint WinterHack — Top 10 Teams Pitching Session we are excited for pit...
bybajpaitusharoffon678
 
PDF
"When every team does things "right", but together it turns into chaos", Yozh...
byFwdays
 
PDF
Web3 - Applications and Architectures - History and Horizons
byGokul Alex
 
PDF
Fortinet Certified Fundamentals in Cybersecurity
byVICTOR MAESTRE RAMIREZ
 
PDF
The Enterprise Web3 Landscape - a view from Kaleido based on the past 10 year...
byPeter Broadhurst
 
PDF
A Simple Guide to Real Estate Tokenization on XRP Ledger.pdf
byemmajoh2025
 
PDF
Real-Time AI Masterclass: Vector Search at Scale
byScyllaDB
 
PDF
Transcript: EU regulations for the North American book supply chain - Tech Fo...
byBookNet Canada
 
PDF
Real-Time AI at Scale Masterclass: Feature Store at Scale
byScyllaDB
 
PDF
Dev Dives: Build and deploy agentic automations - the unified way
byUiPathCommunity
 
PDF
Peculiar Findings Around CEX Activity and ETH Price
bytobbymnbvcxz
 
PDF
EU regulations for the North American book supply chain - Tech Forum 2026
byBookNet Canada
 
Computer-Based Training (CBT) The Backbone of Modern Technical & Defence Trai...
bycomputerbasedtrainin1
 
ICT500 - CRITICAL AND CREATIVE THINKING FOR INFORMATION TECHNOLOGY SOLUTIONS:...
by2024432452
 
Build Next-Gen Spatial & Sensor Workflows: Secure, Scalable Processing in Sno...
bySafe Software
 
React Mastery: Visual Mental Models to Understand React Deeply
byThomas Gaye
 
Adapt.com Seed Fundraising Deck | The AI Computer for Business
byashley459565
 
Certified AI-Native Foundations Professional.pdf
byMarc Entsminger SPC6, RTE, SSM, SA, SDP
 
7 Essential Types of Penetration Testing Services Every Business Should Under...
bypandeydevika621
 
Software Engineering in the Age of AI Agents
byHusseinMalikMammadli
 
TechSprint WinterHack — Top 10 Teams Pitching Session we are excited for pit...
bybajpaitusharoffon678
 
"When every team does things "right", but together it turns into chaos", Yozh...
byFwdays
 
Web3 - Applications and Architectures - History and Horizons
byGokul Alex
 
Fortinet Certified Fundamentals in Cybersecurity
byVICTOR MAESTRE RAMIREZ
 
The Enterprise Web3 Landscape - a view from Kaleido based on the past 10 year...
byPeter Broadhurst
 
A Simple Guide to Real Estate Tokenization on XRP Ledger.pdf
byemmajoh2025
 
Real-Time AI Masterclass: Vector Search at Scale
byScyllaDB
 
Transcript: EU regulations for the North American book supply chain - Tech Fo...
byBookNet Canada
 
Real-Time AI at Scale Masterclass: Feature Store at Scale
byScyllaDB
 
Dev Dives: Build and deploy agentic automations - the unified way
byUiPathCommunity
 
Peculiar Findings Around CEX Activity and ETH Price
bytobbymnbvcxz
 
EU regulations for the North American book supply chain - Tech Forum 2026
byBookNet Canada
 

Specification by Example

  • 1.
    Specification By Example Declan Whelan @dwhelan
  • 2.
  • 3.
  • 4.
    Waterfall X Source: http://www.cs.umd.edu/class/spring2003/cmsc838p/Process/waterfall.pdf
  • 5.
    Cost Of Change Cost% Of% Change% Time%
  • 6.
    Agile Specification Agile&Approach& Itera/on&1& Itera/on&2& Itera/on&3& Itera/on&4& Requirements& Requirements& Requirements& Requirements& Analysis&&&Design& Analysis&&&Design& Analysis&&&Design& Analysis&&&Design& Cost% of% Code& Code& Code& Code& Change% Test& Test& Test& Test& Deploy& Time%
  • 7.
  • 8.
  • 9.
    Traditional Flow Build Specification
  • 10.
    Traditional Flow Build Specification Tests Cases
  • 11.
    Traditional Flow Build Specification Test Tests Cases
  • 12.
    Traditional Flow Build Specification Test Deploy Tests Cases
  • 13.
    We Found aBug! How did QA miss this? That was obvious! I shouldn't Developers don't test before have to spell out every they throw it over the wall! detail! Exec Tester Product Manager We did what was in functional spec! Business requirements weren't clear! BA missed it in the technical requirements! Dev BA Architect
  • 14.
    We Found aBug! How did QA miss this? That was obvious! I shouldn't Developers don't test before have to spell out every they throw it over the wall! detail! Exec Tester Product Manager We did what was in functional spec! Business requirements weren't clear! BA missed it in the technical requirements! Dev BA Architect
  • 15.
    We Found aBug! How did QA miss this? That was obvious! I shouldn't Developers don't test before have to spell out every they throw it over the wall! detail! Exec Tester Product Manager We did what was in functional spec! Business requirements weren't clear! BA missed it in the technical requirements! Dev BA Architect
  • 16.
    We Found aBug! How did QA miss this? That was obvious! I shouldn't Developers don't test before have to spell out every they throw it over the wall! detail! Exec Tester Product Manager We did what was in functional spec! Business requirements weren't clear! BA missed it in the technical requirements! Dev BA Architect
  • 17.
    We Found aBug! How did QA miss this? That was obvious! I shouldn't Developers don't test before have to spell out every they throw it over the wall! detail! Exec Tester Product Manager We did what was in functional spec! Business requirements weren't clear! BA missed it in the technical requirements! Dev BA Architect
  • 18.
    We Found aBug! How did QA miss this? That was obvious! I shouldn't Developers don't test before have to spell out every they throw it over the wall! detail! Exec Tester Product Manager We did what was in functional spec! Business requirements weren't clear! BA missed it in the technical requirements! Dev BA Architect
  • 19.
    We Found aBug! How did QA miss this? That was obvious! I shouldn't Developers don't test before have to spell out every they throw it over the wall! detail! Exec Tester Product Manager We did what was in functional spec! Business requirements weren't clear! BA missed it in the technical requirements! Dev BA Architect
  • 20.
    Accidental Adversaries + Testing + New Bugs - + - + Testing Additional Development Software Fix Success Tests Success + - + - New Build + Development +
  • 21.
  • 22.
    Functional Silos X Source: http://www.danpontefract.com/images/silo.jpg
  • 23.
    Build it Right Build the Right Thing Specification By Example Gojko Adzic, 2011 page 4
  • 24.
    Build it Right Build the Right Thing Useless Crap Specification By Example Gojko Adzic, 2011 page 4
  • 25.
    Build it Right Business Failure Build the Right Thing Useless Crap Specification By Example Gojko Adzic, 2011 page 4
  • 26.
    Build it Right Business Failure Build the Right Thing Useless Crap Maintenance Nightmare Specification By Example Gojko Adzic, 2011 page 4
  • 27.
    Build it Right Business Failure Business Success Build the Right Thing Useless Crap Maintenance Nightmare Specification By Example Gojko Adzic, 2011 page 4
  • 28.
    Build it Right Business Failure Business Success Specification By Example Build the Right Thing Useless Crap Maintenance Nightmare Specification By Example Gojko Adzic, 2011 page 4
  • 29.
  • 30.
    What are Specifications By Example? • Thin slices of system behaviour • that deliver business value • described as concrete examples • that are potentially automatable • without translation • to create executable specifications • captured in live documentation.
  • 31.
  • 32.
  • 33.
  • 34.
    Specification By Example Business Goal Derive the scope Scope
  • 35.
    Specification By Example Business Goal Derive the scope Scope Specify collaboratively Key Examples
  • 36.
    Specification By Example Business Goal Derive the scope Scope Specify collaboratively Key Examples Refine the specification Specification With Examples
  • 37.
    Specification By Example Business Goal Derive the scope Scope Specify collaboratively Key Examples Refine the specification Specification With Examples Automate literally Executable Specification
  • 38.
    Specification By Example Business Goal Derive the scope Scope Specify collaboratively Key Examples Refine the specification Specification With Examples Automate literally Executable Specification Validate frequently Living Documentation
  • 39.
    Specification By Example Business Goal Derive the scope Scope Shared Understanding Ubiquitous Language Specify collaboratively Key Examples Refine the specification Specification With Examples Automate literally Executable Specification Validate frequently Living Documentation
  • 40.
    Source: https://docs.google.com/drawings/d/1cbfKq-KazcbMVCnRfih6zMSDBdtf90KviV7l2oxGyWM/edit Specification By Example Business Goal Derive the scope Scope Shared Understanding Ubiquitous Language Specify collaboratively Key Examples Refine the specification Specification With Examples Automate literally Executable Specification Validate frequently Living Documentation
  • 41.
    Derive the Scope:Story Mapping Source: http://availagility.co.uk/wp-content/uploads/2008/10/user-story-mapping.png
  • 42.
    Derive the Scope:User Stories
  • 43.
    Derive the Scope:User Stories As a _______ I want to _______ So that _______
  • 44.
    Derive the Scope:User Stories As a _______ I want to _______ So that _______ As a student I want to purchase used books online So that I can save money
  • 45.
  • 46.
  • 47.
    Specify Collaboratively: Workshops • Hold regular product backlog workshops
  • 48.
    Specify Collaboratively: Workshops • Hold regular product backlog workshops • Full team workshops - when starting
  • 49.
    Specify Collaboratively: Workshops • Hold regular product backlog workshops • Full team workshops - when starting • Three amigo workshops: • One developer • One tester • One analyst
  • 50.
  • 51.
    Specify Collaboratively: KeyExamples Given _______ When _______ Then _______
  • 52.
    Specify Collaboratively: KeyExamples Given _______ When _______ Then _______ Given “War and Peace” is available as a used book for $2.99 When Susan selects book“War and Peace” Then “Buy used for $2.99” is displayed
  • 53.
  • 54.
    Refining the Specification “Specificationswith examples are acceptance tests” Gojko Adzic
  • 55.
    Refining the Specification “Specificationswith examples are acceptance tests” Gojko Adzic • Be precise and make sure spec is testable
  • 56.
    Refining the Specification “Specificationswith examples are acceptance tests” Gojko Adzic • Be precise and make sure spec is testable • Avoid “scripts” and “flows”
  • 57.
    Refining the Specification “Specificationswith examples are acceptance tests” Gojko Adzic • Be precise and make sure spec is testable • Avoid “scripts” and “flows” • Focus on business functionality not design
  • 58.
    Refining the Specification “Specificationswith examples are acceptance tests” Gojko Adzic • Be precise and make sure spec is testable • Avoid “scripts” and “flows” • Focus on business functionality not design • Avoid UI details
  • 59.
    Refining the Specification “Specificationswith examples are acceptance tests” Gojko Adzic • Be precise and make sure spec is testable • Avoid “scripts” and “flows” • Focus on business functionality not design • Avoid UI details • Avoid covering every possible combination
  • 60.
    Refining the Specification:An Example Free Delivery Free delivery is offered to VIP customers once they purchase a certain number of books. Free delivery is not offered to regular customers or VIP customers buying anything other than books. Customer Type Cart Contents Delivery VIP 5 books Free, Standard VIP 4 books Standard Regular 10 books Standard VIP 5 dishwashers Standard VIP 5 books, 1 dishwasher Standard Source: Specification by Example: How successful teams deliver the right software, Gojko Adzic, pg. 116
  • 61.
  • 62.
  • 63.
    Automating Examples • Startsmall • Select important examples for automation
  • 64.
    Automating Examples • Startsmall • Select important examples for automation • Plan up-front to automate
  • 65.
    Automating Examples • Startsmall • Select important examples for automation • Plan up-front to automate • Be prepared to go slower at the start
  • 66.
    Automating Examples • Startsmall • Select important examples for automation • Plan up-front to automate • Be prepared to go slower at the start • Treat automation code as a first class citizen
  • 67.
    Automating Examples • Startsmall • Select important examples for automation • Plan up-front to automate • Be prepared to go slower at the start • Treat automation code as a first class citizen • Avoid record and playback
  • 68.
    Automating Examples • Startsmall • Select important examples for automation • Plan up-front to automate • Be prepared to go slower at the start • Treat automation code as a first class citizen • Avoid record and playback • Avoid using pre-populated data
  • 69.
  • 70.
    Automation Tools FitNesse Cucumber Concordian Green JBehave Twist Pepper Robot Text Test SpecFlow Framework
  • 71.
  • 72.
    Validate Frequently • Startwith a Continuous Integration system
  • 73.
    Validate Frequently • Startwith a Continuous Integration system • Set up a Continuous Deployment system
  • 74.
    Validate Frequently • Startwith a Continuous Integration system • Set up a Continuous Deployment system • Specify and test business logic separately from end-to-end flows
  • 75.
    Validate Frequently • Startwith a Continuous Integration system • Set up a Continuous Deployment system • Specify and test business logic separately from end-to-end flows • Organize tests along functional lines
  • 76.
    Validate Frequently • Startwith a Continuous Integration system • Set up a Continuous Deployment system • Specify and test business logic separately from end-to-end flows • Organize tests along functional lines • Run all test nightly
  • 77.
    Validate Frequently • Startwith a Continuous Integration system • Set up a Continuous Deployment system • Specify and test business logic separately from end-to-end flows • Organize tests along functional lines • Run all test nightly • Consider an iteration “test pack”
  • 78.
    Living Documentation • Keepspecifications short • Evolve a specification language and leverage in with “common fixtures” • Make documentation accessible - consider a wiki • Organize the documentation • Put specifications under version control
  • 79.
  • 80.
  • 81.
    Cucumber Organization fixtures are common Features Step System
  • 82.
    Cucumber Organization fixtures are common ad Lo Features Step System
  • 83.
    Cucumber Organization fixtures are common M ad at Lo ch Features Step System
  • 84.
    Cucumber Organization fixtures are common M ad at Lo ch Features Step Call System
  • 85.
    Feature File Feature: Turn cucumber into beer As a cucumber presenter I want beer after my presentation So I can enjoy the rest of DemoCampGuelph Scenario: Brydon buys Declan beer Given Brydon hosts DemoCampGuelph When Declan demos Cucumber Then Brydon should buy Declan 1 beer Scenario: Ali buys Declan beer Given Ali hosts DemoCampGuelph When Declan demos Cucumber Then Ali should buy Declan 1 beer
  • 86.
    Step Definitions Given /^(.+)hosts/ do |host| @event = Event.new(host) end When /^(.+) demos/ do |presenter| @event.add(presenter) end Then /^(.+) should buy (.+) (d+) (.*)$/ do |buyer, drinker, qty, item| perk = @event.perks[0]; perk.buyer.should == buyer; perk.receiver.should == drinker perk.quantity.should == quantity.to_i; perk.item.should == item end
  • 87.
    System Under Test class Event attr_reader :perks def initialize(host) @host = host; @perks = [] end def add(presenter) @perks.push Perk.new(@host, presenter, 1, "beer") end end class Perk attr_reader :buyer, :receiver, :quantity, :item def initialize(buyer, receiver, quantity, item) @buyer = buyer; @receiver = receiver @quantity = quantity; @item = item end end
  • 88.
    Execution Scenario: Brydon buysDeclan beer Given Brydon hosts DemoCampGuelph When Declan demos Cucumber Then Brydon should buy Declan 1 beer
  • 89.
    Execution Scenario: Brydon buysDeclan beer Given Brydon hosts DemoCampGuelph When Declan demos Cucumber Then Brydon should buy Declan 1 beer Given /^(.+) hosts/ do | When /^(.+) demos/ do | host| presenter| @event = @event.add(presenter) Event.new(host) end End Then /^(.+) should buy (.+) (d+) (.*)$/ do |buyer, drinker, qty, item| perk = @event.perks[0]; perk.buyer.should == buyer; perk.receiver.should == drinker
  • 90.
    Execution Scenario: Brydon buysDeclan beer Given Brydon hosts DemoCampGuelph When Declan demos Cucumber Then Brydon should buy Declan 1 beer Given /^(.+) hosts/ do | host| @event = Event.new(host) End
  • 91.
    Execution Scenario: Brydon buysDeclan beer Given Brydon hosts DemoCampGuelph When Declan demos Cucumber Then Brydon should buy Declan 1 beer Given /^(.+) hosts/ do | host| “Brydon” @event = Event.new(host) End
  • 92.
    Execution Scenario: Brydon buysDeclan beer Given Brydon hosts DemoCampGuelph When Declan demos Cucumber Then Brydon should buy Declan 1 beer
  • 93.
    Execution Scenario: Brydon buysDeclan beer Given Brydon hosts DemoCampGuelph When Declan demos Cucumber Then Brydon should buy Declan 1 beer Given /^(.+) hosts/ do | When /^(.+) demos/ do | host| presenter| @event = @event.add(presenter) Event.new(host) end End Then /^(.+) should buy (.+) (d+) (.*)$/ do |buyer, drinker, qty, item| perk = @event.perks[0]; perk.buyer.should == buyer; perk.receiver.should == drinker
  • 94.
    Execution Scenario: Brydon buysDeclan beer Given Brydon hosts DemoCampGuelph When Declan demos Cucumber Then Brydon should buy Declan 1 beer When /^(.+) demos/ do | presenter| @event.add(presenter) end
  • 95.
    Execution Scenario: Brydon buysDeclan beer Given Brydon hosts DemoCampGuelph When Declan demos Cucumber Then Brydon should buy Declan 1 beer When /^(.+) demos/ do | presenter| @event.add(presenter) end “Declan”
  • 96.
    Execution Scenario: Brydon buysDeclan beer Given Brydon hosts DemoCampGuelph When Declan demos Cucumber Then Brydon should buy Declan 1 beer
  • 97.
    Execution Scenario: Brydon buysDeclan beer Given Brydon hosts DemoCampGuelph When Declan demos Cucumber Then Brydon should buy Declan 1 beer Given /^(.+) hosts/ do | When /^(.+) demos/ do | host| presenter| @event = @event.add(presenter) Event.new(host) end End Then /^(.+) should buy (.+) (d+) (.*)$/ do |buyer, drinker, qty, item| perk = @event.perks[0]; perk.buyer.should == buyer; perk.receiver.should == drinker
  • 98.
    Execution Scenario: Brydon buysDeclan beer Given Brydon hosts DemoCampGuelph When Declan demos Cucumber Then Brydon should buy Declan 1 beer Then /^(.+) should buy (.+) (d+) (.*)$/ do |buyer, drinker, qty, item| perk = @event.perks[0]; perk.buyer.should == buyer; perk.receiver.should == drinker
  • 99.
    Execution Scenario: Brydon buysDeclan beer Given Brydon hosts DemoCampGuelph When Declan demos Cucumber Then Brydon should buy Declan 1 beer Then /^(.+) should buy (.+) (d+) (.*)$/ do |buyer, drinker, qty, item| perk = @event.perks[0]; perk.buyer.should == buyer; perk.receiver.should == drinker
  • 100.
    Source: https://docs.google.com/drawings/d/1cbfKq-KazcbMVCnRfih6zMSDBdtf90KviV7l2oxGyWM/edit Specification By Example Business Goal Derive the scope Scope Shared Understanding Ubiquitous Language Specify collaboratively Key Examples Refine the specification Specification With Examples Automate literally Executable Specification Validate frequently Living Documentation
  • 101.
    Build it Right Build the Right Thing Specification By Example Gojko Adzic, 2011 page 4
  • 102.
    Build it Right Build the Right Thing Useless Crap Specification By Example Gojko Adzic, 2011 page 4
  • 103.
    Build it Right Business Failure Build the Right Thing Useless Crap Specification By Example Gojko Adzic, 2011 page 4
  • 104.
    Build it Right Business Failure Build the Right Thing Useless Crap Maintenance Nightmare Specification By Example Gojko Adzic, 2011 page 4
  • 105.
    Build it Right Business Failure Business Success Build the Right Thing Useless Crap Maintenance Nightmare Specification By Example Gojko Adzic, 2011 page 4
  • 106.
    Build it Right Business Failure Business Success Specification By Example Build the Right Thing Useless Crap Maintenance Nightmare Specification By Example Gojko Adzic, 2011 page 4
  • 107.
    Reading Specification By Example GojkoAdzic The RSpec Book: Behaviour Driven Development with RSpec, Cucumber and Friends David Cheliminksy et al Agile Testing: A Practical Guide for Testers and Agile Teams Lisa Crispin, Janet Gregory
  • 108.
    Diagram Credits Lisa Crispin and Janet Gregory Agile Testing: A Practical Guide for Testers and Agile Teams Addison-Wesley Professional; January 9, 2009. Mike Cohn Succeeding with Agile: Software Development Using Scrum Addison-Wesley Professional; November 5, 2009.

Editor's Notes