Bdd From The Trenches

BDD FROM THE Luismi Cavallé TRENCHES Jorge Gómez Sancha BeBanjo

As a [Role] I want [Feature] So that [Benefit] Scenario = Acceptance Criteria Given [Context] And [Some more Context] When [Event] And [Some other Event] Then [Outcome] And [Another Outcome]

Given [Context] Planteamiento When [Event] Nudo Then [Outcome] Desenlace

User Stories = Great way to communicate functionality

Searching for “THE WAY” to develop software

We have made good progress...

...but we are always searching

HOW H Y

Friday (afternoon)

What’s the most important thing the system doesn’t do? http://dannorth.net/introducing-bdd

Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature

Feature Feature Feature Feature Feature Feature Feature

Story: User sees timeline for a title As a user, I want to see a timeline of all the events associated to a title, So that I have access to its full history Scenario: An entry in the title timeline gets created when scheduled Given Telefonica operates VOD services Imagenio And a user Borat from the company Telefonica And Pedro scheduled the title Spaceballs on 15-03-2008 in Imagenio When Borat logs in And Borat goes to the title's timeline page for title Spaceballs Then he should see an entry 'Scheduled by Borat' on March 15, 2008

It’s game time

Would you mind giving me some privacy?

Would you mind giving me some privacy? Porras LuisMi

Estimates Features L uismi R J ai orge S ergio A 3 2 4 3 B 1 .5 2 1 C 1 .5 15 . 1 D 15 . 1 15 . 2

Estimates We use these Features L uismi R J ai orge S ergio Average A 3 2 4 3 3 B 1 .5 2 1 11 . C 1 .5 15 . 1 1 D 15 . 1 15 . 2 15 .

Burndown Junkies Functionality Left F M T W Th Time

Black Monday

Progress Ideal Preso ✓ Estimating, Game, Burndown 20 100 Pair Programming 20 75 Acceptance vs Unit 20 50 Upfront Design 10 25 Love 10 0 Productivity 20 40’ 35’ 30’ 25’ 20’ 15’ 10’ 5’ End! Total 100 Left: 80

Monday

“Pair all the fucking time” -- Obie Fernandez

“Aparéate todo el puto día” -- BeBanjo

# /bebanjo_app/features/login.feature Scenario: User logs in successfully Given an existing user Robert with password 'r0b3rt' When Robert logs in entering the password 'r0b3rt' Then he should be redirected to the home page

$ cd bebanjo_app

$ cd bebanjo_app $ script/cucumber features/login.feature

$ cd bebanjo_app $ script/cucumber features/login.feature Scenario: User logs in successfully Given an existing user Robert with password 'r0b3rt' [PENDING] When Robert logs in entering the password 'r0b3rt' [PENDING] Then he should be redirected to the home page [PENDING]

# /bebanjo_app/features/steps/user_steps.rb

# /bebanjo_app/features/steps/user_steps.rb Given /^an existing user (.*) with password '(.*)'$/ do |username, password|

# /bebanjo_app/features/steps/user_steps.rb Given /^an existing user (.*) with password '(.*)'$/ do |username, password| User.create(:username => username, :password => password)

# /bebanjo_app/features/steps/user_steps.rb Given /^an existing user (.*) with password '(.*)'$/ do |username, password| User.create(:username => username, :password => password) end

$ script/cucumber features/login.feature

$ script/cucumber features/login.feature Scenario: User logs in successfully Given an existing user Robert with password 'r0b3rt' [FAILED] uninitialized constant User (NameError) When Robert logs in entering the password 'r0b3rt' [PENDING] Then he should be redirected to the home page [PENDING]

$ script/generate model User username:string password:string

$ script/generate model User username:string password:string $ rake db:migrate && rake db:test:prepare

$ script/cucumber features/login.feature Scenario: User logs in successfully Given an existing user Robert with password 'r0b3rt' When Robert logs in entering the password 'r0b3rt' [PENDING] Then he should be redirected to the home page [PENDING]

# /bebanjo_app/features/steps/user_steps.rb When /^(.*) logs in entering the password '(.*)'$/ do |username, password|

# /bebanjo_app/features/steps/user_steps.rb When /^(.*) logs in entering the password '(.*)'$/ do |username, password| visits quot;/session/newquot;

# /bebanjo_app/features/steps/user_steps.rb When /^(.*) logs in entering the password '(.*)'$/ do |username, password| visits quot;/session/newquot; fills_in quot;Usernamequot;, :with => username

# /bebanjo_app/features/steps/user_steps.rb When /^(.*) logs in entering the password '(.*)'$/ do |username, password| visits quot;/session/newquot; fills_in quot;Usernamequot;, :with => username fills_in quot;Passwordquot;, :with => password

# /bebanjo_app/features/steps/user_steps.rb When /^(.*) logs in entering the password '(.*)'$/ do |username, password| visits quot;/session/newquot; fills_in quot;Usernamequot;, :with => username fills_in quot;Passwordquot;, :with => password clicks_button quot;Sign inquot;

# /bebanjo_app/features/steps/user_steps.rb When /^(.*) logs in entering the password '(.*)'$/ do |username, password| visits quot;/session/newquot; fills_in quot;Usernamequot;, :with => username fills_in quot;Passwordquot;, :with => password clicks_button quot;Sign inquot; end

$ script/cucumber features/login.feature Scenario: User logs in successfully Given an existing user Robert with password 'r0b3rt' When Robert logs in entering the password 'r0b3rt' [FAILED] No route matches quot;/session/newquot; with {:method=>:get} (RoutingError) Then he should be redirected to the home page [PENDING]

# /bebanjo_app/config/routes.rb ActionController::Routing::Routes.draw do |map| map.resource :session

# /bebanjo_app/app/controllers/sessions_controller.rb

# /bebanjo_app/app/controllers/sessions_controller.rb class SessionsController < ApplicationController

# /bebanjo_app/app/controllers/sessions_controller.rb class SessionsController < ApplicationController def new

# /bebanjo_app/app/controllers/sessions_controller.rb class SessionsController < ApplicationController def new end

# /bebanjo_app/app/controllers/sessions_controller.rb class SessionsController < ApplicationController def new end def create

# /bebanjo_app/app/controllers/sessions_controller.rb class SessionsController < ApplicationController def new end def create end

# /bebanjo_app/app/controllers/sessions_controller.rb class SessionsController < ApplicationController def new end def create end end

# /bebanjo_app/app/views/sessions/new.html.erb <% form_for :session, :url => session_path do |f| -%> <%= f.label :username %>: <%= f.text_field :username %> <%= f.label :password %>: <%= f.password_field :password %> <%= f.submit quot;Sign inquot; %> <% end -%>

$ script/cucumber features/login.feature Scenario: User logs in successfully Given an existing user Robert with password 'r0b3rt' When Robert logs in entering the password 'r0b3rt' Then he should be redirected to the home page [PENDING]

# /bebanjo_app/features/steps/user_steps.rb Then /^(?:he|she) should be redirected to the home page$/ do response.request.path.should == quot;/quot; end

$ script/cucumber features/login.feature Scenario: User logs in successfully Given an existing user Robert with password 'r0b3rt' When Robert logs in entering the password 'r0b3rt' Then he should be redirected to the home page [FAILED] expected redirect to quot;/quot;, got no redirect (ExpectationNotMetError)

# /bebanjo_app/app/controllers/sessions_controller.rb class SessionsController < ApplicationController def new end def create redirect_to root_path end end

$ script/cucumber features/login.feature Scenario: User logs in successfully Given an existing user Robert with password 'r0b3rt' When Robert logs in entering the password 'r0b3rt' Then he should be redirected to the home page 3 steps passed

# /bebanjo_app/features/login.feature Scenario: User logs in with incorrect credentials Given an existing user Robert with password 'r0b3rt' When Robert logs in entering the password 'robert' Then he should not be redirected to the home page

$ git commit -a -m “Scenario: User logs in successfully”

$ git commit -a -m “Scenario: User logs in successfully” $ git push origin master

Story driven Swapping Criteria

Increased Focus Knowledge share Pride Effect

Progress Ideal Preso ✓ Estimating, Game, Burndown 20 100 ✓ Pair Programming 20 75 Acceptance vs Unit 20 50 Upfront Design 10 25 Love 10 0 Productivity 20 40’ 35’ 30’ 25’ 20’ 15’ 10’ 5’ End! Total 100 Left: 60

Tuesday

Acceptance Unit

Acceptance Unit Development / Design Great veriﬁcation tool tool

Acceptance

# user_steps.rb Given /^an existing user (.*)$/ do |username| create_user(:username => username) end

# user_steps.rb Given /^an existing user (.*)$/ do |username| create_user(:username => username) end # example_data.rb (fixture_replacement) attributes_for :user do |u| u.username = String.random u.password = quot;secretquot; u.password_confirmation = quot;secretquot; u.company = default_company end

# user_steps.rb When /^(.*) logs in$/ do |username| visits quot;/session/newquot; fills_in quot;Usernamequot;, :with => username fills_in quot;Passwordquot;, :with => quot;secretquot; clicks_button quot;Sign inquot; end

# user_steps.rb Then /^the email of (.*) should be (.*)/ do |username, email| user = User.find_by_username(username) user.email.should == email # assert_equal(email, user.email) end

# user_steps.rb Then /^the email of (.*) should be (.*)/ do |username, email| user = User.find_by_username(username) user.email.should == email # assert_equal(email, user.email) end Then /^the user should see the title (.*)/ do |title| response.should have_tag(quot;.titlequot;, title) # assert_select(quot;.titlequot;, title) end

Acceptance testing is great...

Acceptance testing is great... • as a veriﬁcation tool

Acceptance testing is great... • as a veriﬁcation tool • as a bridge between user needs and automated tests

Acceptance testing is great... • as a veriﬁcation tool • as a bridge between user needs and automated tests ...but as a development tool....

Acceptance testing is great... • as a veriﬁcation tool • as a bridge between user needs and automated tests ...but as a development tool.... • it is not easy to debug

Acceptance testing is great... • as a veriﬁcation tool • as a bridge between user needs and automated tests ...but as a development tool.... • it is not easy to debug • it is slow to run

Acceptance testing is great... • as a veriﬁcation tool • as a bridge between user needs and automated tests ...but as a development tool.... • it is not easy to debug • it is slow to run • it doesn’t encourage good design

Acceptance testing is great... • as a veriﬁcation tool • as a bridge between user needs and automated tests ...but as a development tool.... • it is not easy to debug • it is slow to run • it doesn’t encourage good design • it is not comprehensive

Acceptance testing is great... • as a veriﬁcation tool • as a bridge between user needs and automated tests ...but as a development tool.... • it is not easy to debug • it is slow to run • it doesn’t encourage good design • it is not comprehensive ...so we need something more

RSpec offers lots of possibilities:

RSpec offers lots of possibilities: Model specs Controller specs View specs Helper specs Routes specs

RSpec offers lots of possibilities: Model specs Controller specs Interaction-based View specs State-based Helper specs Structure-based Routes specs

But we’re only interested in: Maximize Productivity Maximize Quality

So, how do we spec... Our Views?

So, how do we spec... Our Views? We mostly don’t

So, how do we spec... Our Views? We mostly don’t Redundant with “then” steps in stories

So, how do we spec... Our Controllers?

So, how do we spec... Our Controllers? 67% Coverage

So, how do we spec... Our Controllers? 67% Coverage Interaction-based unit test

So, how do we spec... Our Controllers? 67% Coverage Interaction-based unit test Still discussing if it is worth

# tasks_controller_spec.rb describe quot;POST 'create'quot; do before(:each) do @task_attibutes = stub(Hash) @task = stub(Task) @tasks.stub!(:create).and_return(@task) end def do_post post :create, :scheduled_title_id => 1, :task => @task_attributes end it quot;should get the scheduled title from the current companyquot; do @scheduled_titles.should_receive(:find).with(quot;1quot;).and_return(@scheduled_title) do_post end it quot;should create the taskquot; do @tasks.should_receive(:create).with(@task_attributes) do_post end it quot;should redirect to workflowquot; do do_post assigns[:task].should == @task end end

So, how do we spec... Our Models?

So, how do we spec... Our Models? 87% Coverage

So, how do we spec... Our Models? 87% Coverage State-based functional test

So, how do we spec... Our Models? 87% Coverage State-based functional test Only the interesting behavior

describe ScheduledTitle do describe quot;late?quot; do it quot;should be late if begins_at is in the pastquot; do scheduled_title = new_scheduled_title(:begins_at => Date.today - 3.days) scheduled_title.should be_late end it quot;should not be late if begins_at is in the futurequot; do scheduled_title = new_scheduled_title(:begins_at => Date.today + 3.days) scheduled_title.should_not be_late end it quot;should not be late if begins_at is todayquot; do scheduled_title = new_scheduled_title(:begins_at => Date.today) scheduled_title.should_not be_late end end

So, how do we spec... Other objects?

So, how do we spec... Other objects? Helpers -- 32.1% Coverage

So, how do we spec... Other objects? Helpers -- 32.1% Coverage Routes -- never

So, how do we spec... Other objects? Helpers -- 32.1% Coverage Routes -- never Libs -- 86.7%

How do we not spec?

describe User do it { Factory(:user).should have_many(:projects) } it { Factory(:user).should belong_to(:company) } table_has_columns(User, :string, quot;loginquot;) end class User has_many :projects belongs_to :company

describe User do it { Factory(:user).should have_many(:projects) } it { Factory(:user).should belong_to(:company) } table_has_columns(User, :string, quot;loginquot;) end class User create_table quot;usersquot;, :force => true do |t| has_many :projects t.column :login, :string end belongs_to :company

describe User do it { Factory(:user).should have_many(:projects) } it { Factory(:user).should belong_to(:company) } table_has_columns(User, :string, quot;loginquot;) end Structure is not interesting behavior! class User create_table quot;usersquot;, :force => true do |t| has_many :projects t.column :login, :string end belongs_to :company

Progress Ideal Preso ✓ Estimating, Game, Burndown 20 100 ✓ Pair Programming 20 75 ✓ Acceptance vs Unit 20 50 Upfront Design 10 25 Love 10 0 Productivity 20 40’ 35’ 30’ 25’ 20’ 15’ 10’ 5’ End! Total 100 Left: 40

Wednesday

Playboy TV

Progress Ideal Preso ✓ Estimating, Game, Burndown 20 100 ✓ Pair Programming 20 75 ✓ Acceptance vs Unit 20 50 ✓ Upfront Design 10 25 Love 10 0 Productivity 20 40’ 35’ 30’ 25’ 20’ 15’ 10’ 5’ End! Total 100 Left: 30

Thursday

DRY Less code Skinny controller, fat model

Technical debt DRY Less code Skinny controller, fat model

Technical debt Broken windows DRY Less code Skinny controller, fat model

Technical debt Broken windows DRY Less code Skinny controller, fat model Beautiful code

Technical debt Broken windows DRY Less code Skinny controller, fat model Habitable software Beautiful code

Technical debt Broken windows DRY Refactoring towards a deeper insight Less code Skinny controller, fat model Habitable software Beautiful code

Progress Ideal Preso ✓ Estimating, Game, Burndown 20 100 ✓ Pair Programming 20 75 ✓ Acceptance vs Unit 20 50 ✓ Upfront Design 10 25 ✓ Love 10 0 Productivity 20 40’ 35’ 30’ 25’ 20’ 15’ 10’ 5’ End! Total 100 Left: 20

and again, Friday

You call that productivity?

The End

Bdd From The Trenches

by jjggss

Accessibility

Categories

Upload Details

Usage Rights

2 Embeds 20

Statistics

Bdd From The Trenches Presentation Transcript

http://www.slideshare.net	19
http://192.168.10.100	1