RSpec User Stories

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

RSpec and User Stories
A step by step tutorial
By Rahoul Baruah
http://www.brigh...

What is RSpec?
 Behaviour Driven Development
 An evolution of Test Driven Development
 Concentrates on the “behaviour” ...

What are User Stories?
 Acceptance Tests for RSpec
 Describe the functionality of your application
in terms your custo...

A Simple Authentication System
 Write the feature
 Write veriﬁcation code for the feature
 Specify the controller...

Write our Feature
 Write our feature and save it as features/
allow-a-user-to-login.feature
 Show it to the customer a...

 Feature: Allow a User to log in
 As a user,
 I want to log in,
 So I can see my stuff
 Scenario: Success...

rake features
 When we run ‘rake features’ it tells us that
none of the features are implemented
 So we start with the...

Steps - proving a feature works
 Create Ruby ﬁles, registration-steps.rb and
session-steps.rb, in features/steps
 Thes...

registration and session steps
Given /^a user called (.*) with a password of (.*)$/ do | username, password |
user = U...

Specify our Controller
 ‘rake features’ fails
 So we need to start writing some code to make it pass
 But before ...

describe RegistrationsController do
describe quot;GET newquot; do
it quot;should show the form to allow someone to r...

Cont’d…

it quot;should fail to create a new user if given invalid valuesquot; do
on_posting_to :create, :us...

Speciﬁcation for new registrations

 Use helper methods to make the speciﬁcation easier to read
 Use mock objects so we ...

def expect_to_create_a_blank_user
@user = mock_model User
User.should_receive(:new).and_return(@user)
end

def ex...

Implement the Controller
 We do need to build a model…
ruby script/generate rspec_model User

…so that our steps will ...

Implementing the Controller
class RegistrationsController < ApplicationController
def new
@user = User.new
end

...

Specifying the Model
 Now we have our controller behaving as
speciﬁed we need to specify the behaviour of
our User mo...

Specifying the Model
 We write the specs
 Update the migration to deal with the ﬁelds we
need
 We switch the model ba...

Specifying the Model
First attempt…
describe User do
it quot;should have a usernamequot; do
@user = User.new :username...

Cont’d…

it quot;should confirm the password before savingquot; do
@user = User.new :password => 'secret', :passwor...

Specifying the Model
 There are two areas of the speciﬁcation that “smell
bad”
 Both “it should have a unique username...

 The (imperfect) solution is to use object
‘factories’ that encapsulate knowledge of a
valid model.
 We are still sp...

describe User do
it quot;should have a usernamequot; do
@user = a User, :username => ''
@user.should_not be_valid
...

 Rewritten to use “a Something” and “a_saved
Something” as an object factory
 Each speciﬁcation clause only speciﬁes t...

Acceptance
 By now we should have done enough to let the
ﬁrst step in our story pass its acceptance test
 rake feature...

Appendix
 We have a fork of RSpec for Rails that provides a set of helper
methods: prepare_for_errors_on, on_getting,
...

www.brightbox.co.uk
hello@brightbox.co.uk
twitter.com/brightbox

Share SlideShare

Facebook
Twitter
LinkedIn

Embed

Size (px)

Show related SlideShares at end

WordPress Shortcode

Link

LinkedIn
Facebook
Twitter
Email

Replay

Top clipped slide

1 of 27 Ad

1 of 27 Ad