pickle-has_many_support 0.3.1

data/Rakefile.d/jeweller.rake

@@ -0,0 +1,19 @@
+require 'jeweler'
+require 'pickle/version'
+
+Jeweler::Tasks.new do |s|
+  s.name = "pickle"
+  s.version = Pickle::Version::String
+  s.summary = "Easy model creation and reference in your cucumber features"
+  s.description = "Easy model creation and reference in your cucumber features"
+  s.email = "ian.w.white@gmail.com"
+  s.homepage = "http://github.com/ianwhite/pickle/tree"
+  s.authors = ["Ian White"]
+end
+
+Jeweler::GemcutterTasks.new
+
+namespace :release do
+  desc "release to github and gemcutter"
+  task :all => ['release', 'gemcutter:release']
+end

data/Rakefile.d/rcov.rake

@@ -0,0 +1,18 @@
+require 'spec/rake/spectask'
+require 'spec/rake/verify_rcov'
+
+desc "Generate RCov report"
+Spec::Rake::SpecTask.new(:rcov) do |t|
+  t.spec_files  = FileList['spec/**/*_spec.rb']
+  t.rcov        = true
+  t.rcov_dir    = 'doc/coverage'
+  t.rcov_opts   = ['--text-report', '--exclude', "gems/,features/,/Library,spec/,rcov.rb"] 
+end
+
+namespace :rcov do
+  desc "Verify RCov threshold"
+  RCov::VerifyTask.new(:verify => :rcov) do |t|
+    t.threshold = 98.12
+    t.index_html = 'doc/coverage/index.html'
+  end
+end

data/Rakefile.d/rspec.rake

@@ -0,0 +1,7 @@
+require 'spec/rake/spectask'
+
+desc "Run the specs"
+Spec::Rake::SpecTask.new(:spec) do |t|
+  t.spec_files = FileList['spec/**/*_spec.rb']
+  t.spec_opts  = ["--colour"]
+end

data/Rakefile.d/yard.rake

@@ -0,0 +1,5 @@
+require 'yard'
+  
+YARD::Rake::YardocTask.new(:doc) do |t|
+  t.files   = ['lib/**/*.rb', 'rails_generators/**/*.rb']
+end

data/Todo.txt

@@ -0,0 +1,3 @@
+* add 'scope' steps see http://gist.github.com/239570
+* cleanup path_to_pickle and paths.rb (maybe have poly_pickle_path with same semantics as polymorphic_path, but accepting pickle refs)
+* Translations

data/VERSION

@@ -0,0 +1 @@
+0.3.0

data/features/app/app.rb

@@ -0,0 +1,122 @@
+# Routes
+ActionController::Routing::Routes.draw do |map|
+  map.resources :spoons, :controller => 'default'
+  map.resources :forks, :controller => 'default' do |fork|
+    fork.resources :tines, :controller => 'default' do |tine|
+      tine.resources :comments, :controller => 'default'
+    end
+  end
+  map.resources :users, :controller => 'default'
+end
+
+# Migrations
+ActiveRecord::Migration.suppress_messages do
+  ActiveRecord::Schema.define(:version => 0) do
+    create_table :forks, :force => true do |t|
+      t.string :name
+    end
+    
+    create_table :spoons, :force => true do |t|
+      t.string :name
+      t.boolean :round, :default => true, :null => false
+    end
+    
+    create_table :tines, :force => true do |t|
+      t.belongs_to :fork
+      t.boolean :rusty, :default => false, :null => false
+    end
+    
+    create_table :users, :force => true do |t|
+      t.string :name, :status, :email
+      t.decimal :attitude_score, :precision => 4, :scale => 2
+      t.boolean :has_stale_password, :default => false
+    end
+  end
+end
+
+
+# Factories for these Fork & Spoon
+class Fork < ActiveRecord::Base
+  validates_presence_of :name
+  has_many :tines
+  
+  def completely_rusty?
+    tines.map(&:rusty?).uniq == [true]
+  end
+  
+  def fancy?
+    name =~ /fancy/i
+  end
+end
+
+class Tine < ActiveRecord::Base
+  validates_presence_of :fork
+  belongs_to :fork
+end
+
+# Machinist blueprint for this
+class Spoon < ActiveRecord::Base
+  validates_presence_of :name
+end
+
+# we don't want abstract classes getting in there
+class AbstractUser < ActiveRecord::Base
+  self.abstract_class = true
+end
+
+# No factory or blueprint for this
+class User < AbstractUser
+  validates_presence_of :name
+  
+  def positive_person?
+    !no_attitude? && attitude_score > 0
+  end
+  
+  def no_attitude?
+    attitude_score.nil?
+  end
+end
+
+# controllers
+class DefaultController < ActionController::Base
+  def index
+    render :text => "index: I was invoked with #{request.path}"
+  end
+  
+  def show
+    render :text => "show: I was invoked with #{request.path}"
+  end
+  
+  def new
+    render :text => "new: I was invoked with #{request.path}"
+  end
+  
+  def edit
+    render :text => "edit: I was invoked with #{request.path}"
+  end
+end
+
+# notifiers
+class Notifier < ActionMailer::Base
+  include ActionController::UrlWriter
+  
+  # BC 2.1
+  if respond_to?(:view_paths)
+    view_paths << "#{File.dirname(__FILE__)}/views"
+  else
+    self.template_root = "#{File.dirname(__FILE__)}/views"
+  end
+  
+  def user_email(user)
+    @recipients  = user.email
+    @subject     = 'A user email'
+    @body[:user] = user
+    @body[:path] = user_path(user)
+  end
+  
+  def email(to, subject, body)
+    @recipients  = to
+    @subject     = subject
+    @body[:body] = body
+  end
+end

data/features/app/blueprints.rb

@@ -0,0 +1,11 @@
+# Blueprints
+require 'machinist/active_record'
+
+Sham.spoon_name { |i| "Spoon #{i}" }
+
+Spoon.blueprint do
+  name { Sham.spoon_name }
+end
+
+# reset shams between scenarios
+Before { Sham.reset }

data/features/app/factories.rb

@@ -0,0 +1,23 @@
+# Factories
+require 'factory_girl'
+
+Factory.sequence :fork_name do |n|
+  "fork %d04" % n
+end
+
+Factory.define :fork do |f|
+  f.name { Factory.next(:fork_name) }
+end
+
+Factory.define :tine do |t|
+  t.association :fork
+end
+
+Factory.define :rusty_tine, :class => Tine do |t|
+  t.association :fork
+  t.rusty true
+end
+
+Factory.define :fancy_fork, :class => Fork do |t|
+  t.name { "Fancy " + Factory.next(:fork_name) }
+end

data/features/app/views/notifier/email.erb

@@ -0,0 +1 @@
+<%= @body %>

data/features/app/views/notifier/user_email.erb

@@ -0,0 +1,6 @@
+Dear <%= @user.name %>,
+
+This is where you should go: <%= @path %>
+
+Cheers,
+The Pickle Team

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
+  
+  @wip
+  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,59 @@
+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

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