Aslak Hellesoy Executable User Stories R Spec Bdd
Upcoming SlideShare
Loading in...5
×
 

Aslak Hellesoy Executable User Stories R Spec Bdd

on

  • 7,135 views

 

Statistics

Views

Total Views
7,135
Views on SlideShare
7,093
Embed Views
42

Actions

Likes
7
Downloads
123
Comments
0

5 Embeds 42

http://www.slideshare.net 25
http://agile.soup.io 7
http://www.soup.io 6
http://anton-pirker.at 3
http://www.anton-pirker.at 1

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Aslak Hellesoy Executable User Stories R Spec Bdd Aslak Hellesoy Executable User Stories R Spec Bdd Presentation Transcript

    • Behaviour-Driven Development Writing software that matters Aslak Hellesøy - Chief Scientist - BEKK
    • Stakeholders Programmers Dual audience 2
    • Origin and inspiration JBehave Test Driven FIT Dan North Development Ward Chris Matts Kent Beck Cunningham Example Driven Chelimsky, User Stories Development Hellesøy, Takita, Mike Cohn Brian Marick Astels, Baker Connextra Domain Driven Acceptance- Stories Design Test Driven Several Eric Evans Planning
    • Software development is all about delivering business value 4
    • What’s being used Source: CHAOS report
    • Where errors are introduced Source: CHAOS report
    • BDD: Business value 8
    • Ubiqutous Language 10
    • BDD User Stories Withdraw Cash Role As an Account Holder Operation I want to withdraw cash in an ATM So that I can get cash when the bank is closed 1 Business value
    • Origin: Connextra
    • Challenge: Common understanding of “Done” 13
    • BDD Scenarios Given I have £200 in my account When I ask to withdraw £20 Then I should be given £20 And my balance should be £180 1 Business value
    • ATDP Acceptance-Test Driven Planning Product Backlog Write Iteration Scenarios Planning Iteration N (end) Iteration N+1 (start)
    • TDD Red 1 2 Write a Make the failing test pass test Green ? 3 Write a Refactor passing test
    • Developers don’t know... • Where to start • What to test • What not to test • How much to test in one go • What to call tests • How to fix a broken test • That TDD is about design
    • Outside-In 1 2 3 4 5
    • Downloads Contributors 40,000 100 30,000 75 20,000 50 10,000 25 0 0 June 2007 February 2008 June 2007 February 2008 SVN commits RubyForge rank 3,313.00 40 2,484.75 30 1,656.50 20 828.25 10 0 0 June 2007 February 2008 June 2007 February 2008
    • JRuby << RSpec
    • RSpec consists of 2 parts Story Framework Example Framework
    • RSpec User Stories Story: Log in As a Project contributor I want to log in So that I can see what projects I have access to Scenario: User provides wrong credentials Given I am on the login page When I log in with login nobody and password useless Then I should be informed that my password is incorrect And I should not see aslak.hellesoy on the page Scenario: User provides correct credentials Given I am on the login page When I log in with login aslak.hellesoy and password temporary Then I should see aslak.hellesoy on the page And I should have the opportunity to log out
    • RSpec Examples require 'bowling' describe Bowling do before(:each) do @bowling = Bowling.new end it quot;should score 0 for gutter gamequot; do 20.times { @bowling.hit(0) } @bowling.score.should == 0 end end
    • Outside-In Story: Withdraw Money As an account holder I want to withdraw money 1 So that I can get cash when the bank is closed Scenario: Overdraft account Given an account with -1000 kr When I ask for 200 kr Given the balance should be -1000 kr 2 describe Bank do it quot;should not be creatable with negative balancequot; do lambda do 3 Bank.new(-9) end.should(raise_error(quot;Negative balancequot;)) end 4 end 5
    • Summary • As a <Role>, I want <Operation> So that <Business value> • Given <Known state>, When I <Action>, Then <Expected outcome> • Work Outside-in in the layer onion • Write scenarios and tests bottom up (start with outcome) • Tests are sentences
    • References • http://behaviour-driven.org/ • http://dannorth.net/introducing-bdd/ • http://dannorth.net/whats-in-a-story/ • http://rspec.info/ • http://jtestr.codehaus.org/ • http://jruby.codehaus.org/ • http://blog.aslakhellesoy.com/