judit-pickle 0.4.2

data/features/email/email.feature

@@ -0,0 +1,64 @@
+Feature: I can test emails are sent
+  In order write features with emails as outcomes
+  As a feature writer
+  I want to easily see what emails have been delivered
+  
+  Scenario: Deliver an email, and test it's properties
+    Given an email "Gday" with body: "Gday Mate" is delivered to fred@gmail.com
+    Then 1 email should be delivered
+    And the email should not be delivered to "frood@fmail.com"
+    And the email should have subject: "Gday", to: "fred@gmail.com"
+    And the email should contain "Mate"
+    And the email should not contain "Foo"
+    
+  Scenario: Deliver some emails, restrict scope
+    Given an email "cool" with body: "body1" is delivered to fred@gmail.com
+    And an email "tasty" with body: "body2" is delivered to fred@gmail.com
+    And an email "cool" with body: "body3" is delivered to joe@gmail.com
+    
+    Then 2 emails should be delivered to fred@gmail.com
+    And the 1st email should have subject: "cool"
+    And the 2nd email should have subject: "tasty"
+    
+    And 2 emails should be delivered with subject: "cool"
+    And the 1st email should be delivered to fred@gmail.com
+    And the 2nd email should be delivered to joe@gmail.com
+    
+    And 1 email should be delivered with subject: "cool", to: "fred@gmail.com"
+    
+  Scenario: Deliver some emails, reset deliveries
+    Given an email "cool" with body: "body1" is delivered to fred@gmail.com
+    And all emails have been delivered
+    Then 0 emails should be delivered
+    
+  Scenario: Deliver emails to user
+    Given a user exists with name: "Fred", email: "fred@gmail.com"
+    And the user's email is delivered
+    Then 1 email should be delivered to the user
+    And the email should contain "Dear Fred"
+    And the email should link to the user's page
+
+  Scenario: Following the first link in an email
+  	Given a user exists with name: "Fred", email: "fred@gmail.com"
+  	And an email "cool" with body: "some text <a href='http://example.com/users/1'>example page</a> more text" is delivered to fred@gmail.com
+    Then 1 email should be delivered to the user
+		And I click the first link in the email
+		Then I should be at the user's page
+
+  Scenario: Following a link in an email by url
+  	Given a user exists with name: "Fred", email: "fred@gmail.com"
+  	And an email "cool" with body: "some text <a href='http://example.com/users/1'>example page</a> more text" is delivered to fred@gmail.com
+    Then 1 email should be delivered to the user
+		And I follow "example.com/" in the email
+		Then I should be at the user's page
+
+  Scenario: Following a link in an email by the text
+  	Given a user exists with name: "Fred", email: "fred@gmail.com"
+  	And an email "cool" with body: "some text <a href='http://example.com/users/1'>example page</a> more text" is delivered to fred@gmail.com
+    Then 1 email should be delivered to the user
+		And I follow "example page" in the email
+		Then I should be at the user's page
+		
+  Scenario: Save and open email 
+    Given an email "Gday" with body: "Gday Mate" is delivered to fred@gmail.com
+    Then show me the email

data/features/generator/generators.feature

@@ -0,0 +1,59 @@
+@gen
+Feature: allow pickle to generate steps
+  In order to get going with pickle
+  As a dev
+  I want to be able to generate steps
+
+  Scenario: script/generate pickle on fresh cuke install
+    Given cucumber has been freshly generated
+    When I run "script/generate pickle -f"
+    Then the file features/support/pickle.rb should exist
+    And the file features/support/pickle.rb should match /require 'pickle\/world'/
+    And the file features/step_definitions/pickle_steps.rb should be identical to the local step_definitions/pickle_steps.rb
+    
+  Scenario: script/generate pickle path on fresh cuke install
+    Given cucumber has been freshly generated
+    When I run "script/generate pickle path -f"
+    Then the file features/support/pickle.rb should exist
+    And the file features/support/pickle.rb should match /require 'pickle\/world'/
+    And the file features/support/pickle.rb should match /require 'pickle\/path\/world'/
+    And the file features/step_definitions/pickle_steps.rb should be identical to the local step_definitions/pickle_steps.rb
+    And the file features/support/paths.rb should be identical to the local support/paths.rb
+
+  Scenario: script/generate pickle email on fresh cuke install
+    Given cucumber has been freshly generated
+    When I run "script/generate pickle email -f"
+    Then the file features/support/pickle.rb should exist
+    And the file features/support/pickle.rb should match /require 'pickle\/world'/
+    And the file features/support/pickle.rb should match /require 'pickle\/email\/world'/
+    And the file features/step_definitions/pickle_steps.rb should be identical to the local step_definitions/pickle_steps.rb
+    And the file features/step_definitions/email_steps.rb should be identical to the local step_definitions/email_steps.rb
+    And the file features/support/email.rb should be identical to the local support/email.rb
+
+  Scenario: script/generate pickle path email on fresh cuke install
+    Given cucumber has been freshly generated
+    When I run "script/generate pickle path email -f"
+    Then the file features/support/pickle.rb should exist
+    And the file features/support/pickle.rb should be identical to the local support/pickle.rb
+    And the file features/support/pickle.rb should match /require 'pickle\/world'/
+    And the file features/support/pickle.rb should match /require 'pickle\/path\/world'/
+    And the file features/support/pickle.rb should match /require 'pickle\/email\/world'/
+    And the file features/step_definitions/pickle_steps.rb should be identical to the local step_definitions/pickle_steps.rb
+    And the file features/support/paths.rb should be identical to the local support/paths.rb
+    And the file features/step_definitions/email_steps.rb should be identical to the local step_definitions/email_steps.rb
+    And the file features/support/email.rb should be identical to the local support/email.rb
+
+  Scenario: regenerating pickle
+    Given cucumber has been freshly generated
+    And pickle path email has been freshly generated
+    When I run "script/generate pickle path email -f"
+    Then the file features/support/pickle.rb should match /require 'pickle\/world'/
+    And the file features/support/pickle.rb should match /require 'pickle\/path\/world'/
+    And the file features/support/pickle.rb should match /require 'pickle\/email\/world'/
+    And the file features/step_definitions/pickle_steps.rb should be identical to the local step_definitions/pickle_steps.rb
+    And the file features/support/paths.rb should be identical to the local support/paths.rb
+    And the file features/step_definitions/email_steps.rb should be identical to the local step_definitions/email_steps.rb
+    But the file features/support/pickle.rb should not match /require 'pickle\/world'.*require 'pickle\/world'/
+    And the file features/support/pickle.rb should not match /require 'pickle\/path\/world'.*require 'pickle\/path\/world'/
+    And the file features/support/pickle.rb should not match /require 'pickle\/email\/world'.*require 'pickle\/email\/world'/
+    And the file features/support/email.rb should be identical to the local support/email.rb

data/features/path/models_page.feature

@@ -0,0 +1,44 @@
+Feature: I can visit a page for a model
+  In order to easily go to pages for models I've created
+  As a feature writer
+  I want to be able visit pages their model
+
+  Scenario: create a spoon, go its page
+    Given a spoon exists
+    When I go to the spoon's page
+    Then I should be at the spoon's page
+    And the spoon's page should match route /spoons/:id
+    
+  Scenario: create a spoon, go to its edit page, check lots of different refs to it
+    Given a spoon: "fred" exists
+    When I go to spoon: "fred"'s edit page
+    Then I should be at the 1st spoon's edit page
+    And the 1st spoon's edit page should match route /spoons/:id/edit
+    And the spoon's edit page should match route /spoons/:id/edit
+    And the spoon: "fred"'s edit page should match route /spoons/:id/edit
+    
+  Scenario: go to a fork's nested tines page
+    Given a fork exists
+    When I go to the fork's tines page
+    Then I should be at the fork's tines page
+    And the fork's tines page should match route /forks/:fork_id/tines
+  
+  Scenario: go to a fork's new tine page
+    Given a fork exists
+    When I go to the fork's new tine page
+    Then I should be at the fork's new tine page
+    And the fork's new tine page should match route /forks/:fork_id/tines/new
+    
+  Scenario: go to a tine in fork context page
+    Given a fork exists
+    And a tine exists with fork: the fork
+    When I go to the fork's tine's page
+    Then I should be at the fork's tine's page
+    And the fork's tine's page should match route /forks/:fork_id/tines/:id
+    
+  Scenario: go to a tine's comments in fork context
+    Given a fork exists
+    And a tine exists with fork: the fork
+    When I go to the fork's tine's comments page
+    Then I should be at the fork's tine's comments page
+    And the fork's tine's comments page should match route /forks/:fork_id/tines/:tine_id/comments

data/features/path/named_route_page.feature

@@ -0,0 +1,10 @@
+Feature: I can visit a page by named route
+  In order to nav in my features
+  As a feature writer
+  I want to be able visit named routes
+
+  Scenario: visit the new spoons page
+    When I go to the new spoon page
+    Then I should be at the new spoon page
+    And the new spoon page should match route /spoons/new
+   

data/features/pickle/create_from_active_record.feature

@@ -0,0 +1,76 @@
+Feature: I can easily create models from my blueprints
+
+  As a plain old AR user
+  I want to be able to create models with fields
+  So that I can create models quickly and easily in my features
+  
+
+  Scenario: I create a user, and see if it looks right
+    Given a user exists with name: "Fred", has_stale_password: true
+    Then the user should not have a status
+    And the user should have a stale password
+    And the user's name should be "Fred"
+    
+  Scenario: I create a user, and see if it looks right
+    Given a user exists with name: "Fred", status: "crayzee"
+    Then a user should exist with name: "Fred"
+    And a user should exist with status: "crayzee"
+    But a user should not exist with name: "Wilma"
+  
+  Scenario: I create a user via a mapping
+    Given I exist with status: "pwned", name: "fred"
+    Then I should have a status
+    And the user: "me" should have a status
+  
+  Scenario: I create positive and negative users
+    Given a user exists with name: "Fred", attitude_score: +5.42
+    And another user exists with name: "Ethel", attitude_score: -10
+		And another user exists with name: "Buddha", attitude_score: 2_000_000
+    Then 3 users should exist
+    And the 1st user should be a positive person
+    And the 2nd user should not be a positive person
+    And the 1st user's attitude_score should be 5.42
+    And the 2nd user's attitude_score should be -10
+		And the 3rd user's attitude_score should be 2_000_000
+  	And the 3rd user's attitude_score should be 2000000
+
+  Scenario: I create nil values
+    Given a user exists with name: "Fred", attitude_score: nil
+    Then 1 users should exist with attitude_score: nil
+    And that user should be the first user
+    And that user should have no attitude
+    And that user's attitude_score should be nil
+    
+  Scenario: create and find using tables
+    Given the following users exist:
+      | name  | status                   |
+      | Jim   | married                  |
+      | Ethel | in a relationship with x |
+    Then the following users should exist:
+      | name  |
+      | Jim   |
+      | Ethel |
+    And the following users should exist:
+      | status                   |
+      | married                  |
+      | in a relationship with x |
+    And the 1st user should be the 3rd user
+    And the 2nd user should be the last user
+    
+    Scenario: create and find using tables with referencable names
+      Given the following users exist:
+        | user | name | status |
+        | Jack | Jack | alone  |
+        | Pete | Pete | dead   |
+      Then the following users should exist:
+        | name |
+        | Jack |
+        | Pete |
+      And the following users should exist:
+        | user    | status |
+        | lonely  | alone  |
+        | rotting | dead   |
+      And the 1st user should be the user: "Jack"
+      And the 2nd user should be the user: "Pete"
+      And the user: "lonely" should be the user: "Jack"
+      And the user: "rotting" should be the user: "Pete"

data/features/pickle/create_from_factory_girl.feature

@@ -0,0 +1,63 @@
+Feature: I can easily create models from my factories
+
+  As a pickle user
+  I want to be able to leverage my factories
+  So that I can create models quickly and easily in my features
+  
+  Scenario: I create a fork, and see if it looks right
+    Given a fork exists
+    Then the fork should not be completely rusty
+    
+  Scenario: I create a fork, and see if it looks right
+    Given a fork exists with name: "Forky"
+    Then a fork should exist with name: "Forky"
+    And the fork should not be completely rusty
+    
+  Scenario: I create some forks, and some tines
+    Given a fork: "one" exists
+    And a tine exists with fork: fork "one"
+    And another tine exists with fork: fork "one"
+    
+    And a fancy fork exists
+    And a tine exists with fork: the fancy fork
+    
+    Then the first tine should be tine of the fork: "one"
+    And the 2nd tine should be tine of fork: "one"
+    And the last tine should be tine of the fancy fork
+
+    Then the first tine should be in fork "one"'s tines
+    And the 2nd tine should be in fork: "one"'s tines
+    And the last tine should be in the fancy fork's tines
+    And the fancy fork should be the last tine's fork
+    
+    But the first tine should not be in the fancy fork's tines
+    And the last tine should not be in fork "one"'s tines
+    And the fancy fork should not be the first tine's fork
+    
+  Scenario: I create a fork with a tine, and find the tine by the fork
+    Given a fork exists
+    And a tine exists with fork: the fork
+    
+    Then a tine should exist with fork: the fork
+  
+  Scenario: create a tine with fork refs in a table
+    Given 2 forks exist
+    And the following tines exist:
+      | fork         |
+      | the 1st fork |
+      | the 2nd fork |
+      | the 2nd fork |
+    Then the 1st tine should be in the 1st fork's tines
+    And the 2nd tine should be in the 2nd fork's tines
+		And the 3rd tine should be in the 2nd fork's tines
+		And the 1st fork should have 1 tines
+		And the 2nd fork should have 2 tines
+
+  Scenario: I create fork via a mapping
+    Given killah fork exists
+    Then the fork should be fancy
+    And the fancy fork: "of cornwood" should be fancy
+    
+  Scenario: create a tine with a missing fork
+    Then the following should raise Pickle::Session::ModelNotKnownError: "Given a tine exists with fork: the fork"
+    

data/features/pickle/create_from_machinist.feature

@@ -0,0 +1,39 @@
+Feature: I can easily create models from my blueprints
+
+  As a machinist user
+  I want to be able to leverage my blueprints
+  So that I can create models quickly and easily in my features
+  
+  Scenario: I create a spoon, and see if it looks right
+    Given a spoon exists
+    Then the spoon should be round
+    And the spoon's round should be true
+
+  Scenario: I create a non round spoon, and see if it looks right
+    Given a spoon exists with round: false
+    Then the spoon should not be round
+
+  Scenario: I create a named spoon, and see if it has the name
+    Given a spoon exists with name: "Pete", round: false
+    Then a spoon should exist with name: "Pete"
+    And the spoon should not be round
+  
+  Scenario: I create 7 spoons of various roundness
+    Given 2 spoons exist with round: false
+    And 2 spoons exist with round: true
+    And a spoon exists with round: false
+    
+    Then the 1st spoon should not be round
+    And the 2nd spoon should not be round
+    And the 3rd spoon should be round
+    And the 4th spoon should be round
+    And the 5th spoon should not be round
+    
+    And 3 spoons should exist with round: false
+    And the 1st spoon should not be round
+    And the 2nd spoon should not be round
+    And the last spoon should not be round
+    
+    And 2 spoons should exist with round: true
+    And the first spoon should be round
+    And the last spoon should be round

data/features/step_definitions/email_steps.rb

@@ -0,0 +1,63 @@
+# this file generated by script/generate pickle email
+#
+# add email mappings in features/support/email.rb
+
+ActionMailer::Base.delivery_method = :test
+ActionMailer::Base.perform_deliveries = true
+
+Before do
+  ActionMailer::Base.deliveries.clear
+end
+
+# Clear the deliveries array, useful if your background sends email that you want to ignore
+Given(/^all emails? (?:have|has) been delivered$/) do
+  ActionMailer::Base.deliveries.clear
+end
+
+Given(/^(\d)+ emails? should be delivered$/) do |count|
+  emails.size.should == count.to_i
+end
+
+When(/^(?:I|they) follow "([^"]*?)" in #{capture_email}$/) do |link, email_ref|
+  visit_in_email(email(email_ref), link)
+end
+
+When(/^(?:I|they) click the first link in #{capture_email}$/) do |email_ref|
+  click_first_link_in_email(email(email_ref))
+end
+
+Then(/^(\d)+ emails? should be delivered to (.*)$/) do |count, to|
+  emails("to: \"#{email_for(to)}\"").size.should == count.to_i
+end
+
+Then(/^(\d)+ emails? should be delivered with #{capture_fields}$/) do |count, fields|
+  emails(fields).size.should == count.to_i
+end
+
+Then(/^#{capture_email} should be delivered to (.+)$/) do |email_ref, to|
+  email(email_ref, "to: \"#{email_for(to)}\"").should_not be_nil
+end
+
+Then(/^#{capture_email} should not be delivered to (.+)$/) do |email_ref, to|
+  email(email_ref, "to: \"#{email_for(to)}\"").should be_nil
+end
+
+Then(/^#{capture_email} should have #{capture_fields}$/) do |email_ref, fields|
+  email(email_ref, fields).should_not be_nil
+end
+
+Then(/^#{capture_email} should contain "(.*)"$/) do |email_ref, text|
+  email(email_ref).body.should =~ /#{text}/
+end
+
+Then(/^#{capture_email} should not contain "(.*)"$/) do |email_ref, text|
+  email(email_ref).body.should_not =~ /#{text}/
+end
+
+Then(/^#{capture_email} should link to (.+)$/) do |email_ref, page|
+  email(email_ref).body.should =~ /#{path_to(page)}/
+end
+
+Then(/^show me the emails?$/) do
+   save_and_open_emails
+end

data/features/step_definitions/extra_email_steps.rb

@@ -0,0 +1,7 @@
+Given(/^an email "(.*?)" with body: "(.*?)" is delivered to (.+?)$/) do |subject, body, to|
+  Notifier.deliver_email(to, subject, body)
+end
+
+Given(/^#{capture_model}'s email is delivered$/) do |model|
+  Notifier.deliver_user_email(model(model))
+end

data/features/step_definitions/fork_steps.rb

@@ -0,0 +1,4 @@
+# example of making your own matcher with the pickle backend
+Then(/^#{capture_model} should be tine of #{capture_model}$/) do |tine, fork|
+  model(fork).tines.should include(model(tine))
+end

data/features/step_definitions/generator_steps.rb

@@ -0,0 +1,46 @@
+Before('@gen') do
+  `mv #{Rails.root}/features/ #{Rails.root}/features.orig/ > /dev/null 2>&1`
+end
+
+After('@gen') do
+  `rm -rf #{Rails.root}/features`
+  `mv #{Rails.root}/features.orig/ #{Rails.root}/features/ > /dev/null 2>&1`
+end
+
+Given(/^cucumber has been freshly generated$/) do
+  `cd #{Rails.root}; script/generate cucumber -f --webrat`
+end
+
+Given(/^pickle path email has been freshly generated$/) do
+  `cd #{Rails.root}; script/generate -f pickle paths email`
+end
+
+Given(/^env\.rb already requires (.+)$/) do |file|
+  File.open("#{Rails.root}/features/support/env.rb", "a") do |env|
+    env << "require '#{file}'\n"
+  end
+end
+
+When(/^I run "(.*)"$/) do |command|
+  @output = `cd #{Rails.root}; #{command}`
+end
+
+Then(/^I should see "(.*)"$/) do |text|
+  @output.should include(text)
+end
+
+Then(/^the file (.+?) should exist$/) do |file|
+  File.exist?("#{Rails.root}/#{file}").should == true
+end
+
+Then(/^the file (.+?) should match \/(.*?)\/$/) do |file, regexp|
+  File.read("#{Rails.root}/#{file}").should match(/#{regexp}/m)
+end
+
+Then(/^the file (.+?) should not match \/(.*?)\/$/) do |file, regexp|
+  File.read("#{Rails.root}/#{file}").should_not match(/#{regexp}/m)
+end
+
+Then /^the file ([^ ]+) should be identical to the local (.+)$/ do |generated_file, source_file|
+  File.read("#{Rails.root}/#{generated_file}").should == File.read("#{File.dirname(__FILE__)}/../#{source_file}")
+end

data/features/step_definitions/path_steps.rb

@@ -0,0 +1,14 @@
+require File.expand_path(File.join(File.dirname(__FILE__), "..", "support", "paths"))
+
+Then(/^(.+?) should match route \/(.+?)$/) do |page, route|
+  regexp = route.gsub(/:(\w*?)id/,'\d+')
+  path_to(page).should =~ /#{regexp}/
+end
+
+When(/^I go to (.+)$/) do |page|
+  visit path_to(page)
+end
+
+Then(/^I should be at (.+)$/) do |page|
+  request.path.should =~ /#{path_to(page)}/
+end

data/features/step_definitions/pickle_steps.rb

@@ -0,0 +1,100 @@
+# this file generated by script/generate pickle
+
+# create a model
+Given(/^#{capture_model} exists?(?: with #{capture_fields})?$/) do |name, fields|
+  create_model(name, fields)
+end
+
+# create n models
+Given(/^(\d+) #{capture_plural_factory} exist(?: with #{capture_fields})?$/) do |count, plural_factory, fields|
+  count.to_i.times { create_model(plural_factory.singularize, fields) }
+end
+
+# create models from a table
+Given(/^the following #{capture_plural_factory} exists?:?$/) do |plural_factory, table|
+  create_models_from_table(plural_factory, table)
+end
+
+# find a model
+Then(/^#{capture_model} should exist(?: with #{capture_fields})?$/) do |name, fields|
+  find_model!(name, fields)
+end
+
+# not find a model
+Then(/^#{capture_model} should not exist(?: with #{capture_fields})?$/) do |name, fields|
+  find_model(name, fields).should be_nil
+end
+
+# find models with a table
+Then(/^the following #{capture_plural_factory} should exists?:?$/) do |plural_factory, table|
+  find_models_from_table(plural_factory, table).should_not be_any(&:nil?)
+end
+
+# find exactly n models
+Then(/^(\d+) #{capture_plural_factory} should exist(?: with #{capture_fields})?$/) do |count, plural_factory, fields|
+  find_models(plural_factory.singularize, fields).size.should == count.to_i
+end
+
+# assert equality of models
+Then(/^#{capture_model} should be #{capture_model}$/) do |a, b|
+  model!(a).should == model!(b)
+end
+
+# assert model is in another model's has_many assoc
+Then(/^#{capture_model} should be (?:in|one of|amongst) #{capture_model}(?:'s)? (\w+)$/) do |target, owner, association|
+  model!(owner).send(association).should include(model!(target))
+end
+
+# assert model is not in another model's has_many assoc
+Then(/^#{capture_model} should not be (?:in|one of|amongst) #{capture_model}(?:'s)? (\w+)$/) do |target, owner, association|
+  model!(owner).send(association).should_not include(model!(target))
+end
+
+# assert model is another model's has_one/belongs_to assoc
+Then(/^#{capture_model} should be #{capture_model}(?:'s)? (\w+)$/) do |target, owner, association|
+  model!(owner).send(association).should == model!(target)
+end
+
+# assert model is not another model's has_one/belongs_to assoc
+Then(/^#{capture_model} should not be #{capture_model}(?:'s)? (\w+)$/) do |target, owner, association|
+  model!(owner).send(association).should_not == model!(target)
+end
+
+# assert model.predicate? 
+Then(/^#{capture_model} should (?:be|have) (?:an? )?#{capture_predicate}$/) do |name, predicate|
+  if model!(name).respond_to?("has_#{predicate.gsub(' ', '_')}")
+    model!(name).should send("have_#{predicate.gsub(' ', '_')}")
+  else
+    model!(name).should send("be_#{predicate.gsub(' ', '_')}")
+  end
+end
+
+# assert not model.predicate?
+Then(/^#{capture_model} should not (?:be|have) (?:an? )?#{capture_predicate}$/) do |name, predicate|
+  if model!(name).respond_to?("has_#{predicate.gsub(' ', '_')}")
+    model!(name).should_not send("have_#{predicate.gsub(' ', '_')}")
+  else
+    model!(name).should_not send("be_#{predicate.gsub(' ', '_')}")
+  end
+end
+
+# model.attribute.should eql(value)
+# model.attribute.should_not eql(value)
+Then(/^#{capture_model}'s (\w+) (should(?: not)?) be #{capture_value}$/) do |name, attribute, expectation, expected|
+  actual_value  = model(name).send(attribute)
+  expectation   = expectation.gsub(' ', '_')
+  
+  case expected
+  when 'nil', 'true', 'false'
+    actual_value.send(expectation, send("be_#{expected}"))
+  when /^[+-]?[0-9_]+(\.\d+)?$/
+    actual_value.send(expectation, eql(expected.to_f))
+  else
+    actual_value.to_s.send(expectation, eql(eval(expected)))
+  end
+end
+
+# assert size of association
+Then /^#{capture_model} should have (\d+) (\w+)$/ do |name, size, association|
+  model!(name).send(association).size.should == size.to_i
+end

data/features/step_definitions/raise_error_steps.rb

@@ -0,0 +1,3 @@
+Then /^the following should raise Pickle::Session::ModelNotKnownError: "([^"]*)"$/ do |step|
+  lambda { steps step }.should raise_error(Pickle::Session::ModelNotKnownError)
+end

data/features/support/email.rb

@@ -0,0 +1,21 @@
+module EmailHelpers
+  # Maps a name to an email address. Used by email_steps
+
+  def email_for(to)
+    case to
+  
+    # add your own name => email address mappings here
+  
+    when /^#{capture_model}$/
+      model($1).email
+  
+    when /^"(.*)"$/
+      $1
+  
+    else
+      to
+    end
+  end
+end
+
+World(EmailHelpers)