pickle 0.5.0 → 0.5.1

data/spec/pickle/email_spec.rb

@@ -137,30 +137,51 @@ describe Pickle::Email do
   end
 
   describe "following links in emails" do
+    let(:body) { 'some text <a href="http://example.com/page">example page</a> more text' }
+
     before do
       allow(self).to receive(:open_in_browser)
-      allow(@email1).to receive(:body).and_return('some text <a href="http://example.com/page">example page</a> more text')
     end
 
-    it "should find a link for http://example.com/page" do
-      expect(self).to receive(:visit).with('http://example.com/page')
-      visit_in_email(@email1, 'http://example.com/page')
-    end
+    shared_examples_for 'an email with links' do
+      it "should find a link for http://example.com/page" do
+        expect(self).to receive(:visit).with('http://example.com/page')
+        visit_in_email(@email1, 'http://example.com/page')
+      end
+
+      it "should find a link for \"example page\"" do
+        expect(self).to receive(:visit).with('http://example.com/page')
+        visit_in_email(@email1, 'example page')
+      end
+
+      it "should follow the first link in an email" do
+        expect(self).to receive(:visit).with('http://example.com/page')
+        click_first_link_in_email(@email1)
+      end
 
-    it "should find a link for \"example page\"" do
-      expect(self).to receive(:visit).with('http://example.com/page')
-      visit_in_email(@email1, 'example page')
+      it "should not raise an error when the email body is not a string, but needs to_s [#26]" do
+        allow(self).to receive(:visit)
+        allow(@email1).to receive(:body).and_return(:a_string_body)
+        expect { click_first_link_in_email(@email1) }.not_to raise_error
+      end
     end
 
-    it "should follow the first link in an email" do
-      expect(self).to receive(:visit).with('http://example.com/page')
-      click_first_link_in_email(@email1)
+    describe "non multi-part emails" do
+      before do
+        allow(@email1).to receive(:multipart?).and_return(false)
+        allow(@email1).to receive(:body).and_return(body)
+      end
+
+      it_behaves_like 'an email with links'
     end
-    
-    it "should not raise an error when the email body is not a string, but needs to_s [#26]" do
-      allow(self).to receive(:visit)
-      allow(@email1).to receive(:body).and_return(:a_string_body)
-      expect { click_first_link_in_email(@email1) }.not_to raise_error
+
+    context "multi-part emails" do
+      before do
+        allow(@email1).to receive(:multipart?).and_return(true)
+        allow(@email1).to receive_message_chain(:html_part, :body).and_return(body)
+      end
+
+      it_behaves_like 'an email with links'
     end
   end
 end

data/spec/pickle/session_spec.rb

@@ -165,6 +165,22 @@ describe Pickle::Session do
       end
     end
 
+    describe "#create_models" do
+      before do
+        allow(user_factory).to receive(:create).and_return(user)
+      end
+
+      it "should call the factory's create one time for each record" do
+        expect(user_factory).to receive(:create).exactly(10).times
+        create_models(10, "a user")
+      end
+
+      it "should parse the fields only once across all records" do
+        expect(self).to receive(:parse_fields).once
+        create_models(10, "a user")
+      end
+    end
+
     describe "with hash" do
       it "should call user_factory.create({'foo' => 'bar'})" do
         expect(user_factory).to receive(:create).with({'foo' => 'bar'})
@@ -271,7 +287,7 @@ describe Pickle::Session do
 
       it_should_behave_like "after storing a single user"
     end
-    
+
     it "should cope with spaces in the factory name (ie. it should make it canonical)" do
       allow(pickle_parser).to receive(:canonical).and_return('user')
       expect(pickle_parser).to receive(:canonical).with('u ser').and_return('user')
@@ -283,11 +299,11 @@ describe Pickle::Session do
     let(:fred) { double("fred", :class => user_class, :id => 2) }
     let(:shirl) { double("shirl", :class => user_class, :id => 3) }
     let(:noname) { double("noname", :class => user_class, :id => 4) }
-    
+
     if defined? ::FactoryGirl
-      let(:super_admin_factory) { Pickle::Adapter::FactoryGirl.new(double(:build_class => user_class, :name => :super_admin)) }
+      let(:super_admin_factory) { Pickle::Adapter::FactoryGirl.new(double(:build_class => user_class, :name => :super_admin), :super_admin) }
     else
-      let(:super_admin_factory) { Pickle::Adapter::FactoryGirl.new(double(:build_class => user_class, :factory_name => :super_admin)) }
+      let(:super_admin_factory) { Pickle::Adapter::FactoryGirl.new(double(:build_class => user_class, :factory_name => :super_admin), :super_admin) }
     end
 
     before do
@@ -414,7 +430,7 @@ describe Pickle::Session do
       let :ar_class do
         double('ActiveRecord', :column_names => ['user_id', 'user_type'], :const_get => ActiveRecord::Base::PickleAdapter)
       end
-            
+
       it "should return {'user_id' => <the user.id>, 'user_type' => <the user.base_class>}" do
         expect(user.class).to receive(:base_class).and_return(double('User base class', :name => 'UserBase'))
         expect(convert_models_to_attributes(ar_class, :user => user)).to eq({'user_id' => user.id, 'user_type' => 'UserBase'})

metadata

@@ -1,16 +1,15 @@
 --- !ruby/object:Gem::Specification
 name: pickle
 version: !ruby/object:Gem::Version
-  version: 0.5.0
+  version: 0.5.1
 platform: ruby
 authors:
 - Ian White
 - James Le Cuirot
-- Niklas Hofer
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2014-11-16 00:00:00.000000000 Z
+date: 2015-01-12 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: cucumber
@@ -209,7 +208,7 @@ dependencies:
       - !ruby/object:Gem::Version
         version: '0'
 - !ruby/object:Gem::Dependency
-  name: sqlite3-ruby
+  name: sqlite3
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - ">="
@@ -226,7 +225,6 @@ description: Easy model creation and reference in your cucumber features
 email:
 - ian.w.white@gmail.com
 - chewi@aura-online.co.uk
-- niklas+dev@lanpartei.de
 executables: []
 extensions: []
 extra_rdoc_files: []
@@ -238,7 +236,7 @@ files:
 - Gemfile.lock.development
 - History.txt
 - License.txt
-- README.rdoc
+- README.md
 - Rakefile
 - Rakefile.d/cucumber.rake
 - Rakefile.d/release.rake

data/README.rdoc

@@ -1,483 +0,0 @@
-= pickle
-
-{<img src="https://travis-ci.org/ianwhite/pickle.svg" alt="Build Status" />}[https://travis-ci.org/ianwhite/pickle]
-
-Pickle gives you cucumber steps that create your models easily from factory-girl,
-machinist, or fabrication.  You can also just use ActiveRecord as a factory but it's not as cool.
-
-Pickle can make use of different ORMs for finding records.  Currently ActiveRecord, DataMapper, MongoID adapters are
-provided.  More adapters welcome!
-
-References to the models are stored in the current world, not necessarily for the purpose of checking the db
-(although you could use it for that), but for enabling easy reference to urls, and for
-building complex givens which require a bunch of models collaborating
-
-== Quickstart
-
-This is a quickstart guide for rails apps.  Firstly, install {cucumber-rails}[http://github.com/aslakhellesoy/cucumber-rails], and its dependencies.
-Then do the following:
-
-=== Rails 3:
-
-Add the gem to your Gemfile:
-
-  gem 'pickle'
-  
-Then install with:
-
-  bundle install
-  
-Discover the options for the generator:
-
-  rails g pickle --help
-
-Run the generator, e.g:
-
-  rails g pickle --paths --email
-  
-=== For Rails 2:
-
-Add the following to config/environments/cucumber:
-
-  config.gem 'pickle'
-
-Install the gem with
-
-  rake gems:install RAILS_ENV=cucumber
-  
-Run the generator with:
-
-  script/generate pickle [paths] [email]
-
-== Resources
-
-<b>GitHub</b> for code: https://github.com/ianwhite/pickle
-
-<b>RubyGems</b> for the gem: https://rubygems.org/gems/pickle
-
-<b>RubyDoc.info</b> for docs: http://www.rubydoc.info/github/ianwhite/pickle
-
-<b>Google Group</b> for questions: https://groups.google.com/group/pickle-cucumber
-
-<b>Railscast</b> presentation: http://railscasts.com/episodes/186-pickle-with-cucumber
-
-<b>Blog articles</b>: {rubyflare: pickle my cucumber}[http://rubyflare.com/2009/10/28/pickle-my-cucumber/]
-
-
-== Using Pickle
-
-Now have a look at <tt>features/step_definitions/pickle_steps.rb</tt>
-
-If you want path steps and email steps then just add the 'paths' and/or 'email' options to the generator.
-The code/steps will be written to <tt>features/env/paths.rb</tt> and
-<tt>features/step_definitions/email_steps.rb</tt> respectively.
-
-=== Using with plain ole Active Record, DataMapper or Mongoid
-
-Pickle comes with ORM adapters for Active Record, DataMapper and Mongoid.
-
-If you have a model called 'Post', with required fields 'title', and 'body', then you can now write
-steps like this
-
-  Given a post exists with title: "My Post", body: "My body"
-
-=== Using with factory-girl or machinist
-
-But you're using Machinist or FactoryGirl right?!  To leverage all of the factories/blueprints
-you've written, you can just do stuff like
-
-  Given a user exists
-  And another user exists with role: "admin"
-
-  # later
-  Then a user should exist with name: "Fred"
-  And that user should be activated # this uses rspec predicate matchers
-
-==== Machinist: require your blueprints
-
-In your <tt>features/support/env.rb</tt> add the following lines at the bottom
-
-  require "#{Rails.root}/spec/blueprints" # or wherever they live
-
-==== FactoryGirl: make sure factories are loaded
-
-In your config/environments/cucumber.rb file, make sure the factory-girl gem is included (unless it's installed as a plugin).
-
-If that doesn't solve loading issues then require your factories.rb file directly in a file called 'features/support/factory_girl.rb'
-
-  # example features/support/factory_girl.rb
-  require File.dirname(__FILE__) + '/../../spec/factories'
-
-=== Using with an ORM other than ActiveRecord, DataMapper, or Mongoid
-
-Pickle can be used with any modelling library provided there is an adapter written for it.
-
-Adapters are very simple and exist a module or class with the name "PickleAdapter" available to the class.  For example
-
-User.const_get(:PickleAdapter) #=> should return a pickle adapter
-
-The Active Record and DataMapper ones can be found at
-ActiveRecord::Base::PickleAdapter, DataMapper::Resource::PickleAdapter, Mongoid::Document::PickleAdapter respectively.
-
-See how to implement one by looking at the ones provided in the pickle source in lib/pickle/adapters/*
-
-=== Configuring Pickle
-
-You can tell pickle to use another factory adapter (see Pickle::Adapter), or
-create mappings from english expressions to pickle model names.  You can also
-override many of the options on the Pickle::Config object if you so choose.
-
-In: <tt>features/support/pickle.rb</tt>
-
-  require 'pickle/world'
-
-  Pickle.configure do |config|
-    config.adapters = [:machinist, :active_record, YourOwnAdapterClass]
-    config.map 'me', 'myself', 'my', 'I', :to => 'user: "me"'
-  end
-
-Out of the box pickle looks for machinist, factory-girl, then uses the ORM(s) that you're using to create models.
-
-If you find that your steps aren't working with your factories, it's probably the case that your factory setup is not being included in your cucumber environment (see comments above regarding machinist and factory-girl).
-
-== API
-
-=== Steps
-
-When you run <tt>script/generate pickle</tt> you get the following steps
-
-==== Given steps
-
-"Given <b>a model</b> exists",  e.g.
-
-  Given a user exists
-  Given a user: "fred" exists
-  Given the user exists
-
-"Given <b>a model</b> exists with <b>fields</b>",  e.g.
-
-  Given a user exists with name: "Fred"
-  Given a user exists with name: "Fred", activated: false
-  
-This last step could be better expressed by using Machinist/FactoryGirl to create an activated user.  Then you can do
-
-  Given an activated user exists with name: "Fred"
-
-You can refer to other models in the fields
-
-  Given a user exists
-  And a post exists with author: the user
-
-  Given a person "fred" exists
-  And a person "ethel" exists
-  And a fatherhood exists with parent: person "fred", child: person "ethel"
-  
-This last step is given by the default pickle steps, but it would be better written as:
-
-  And "fred" is the father of "ethel"
-  
-It is expected that you'll need to expand upon the default pickle steps to make your features readable.  To write the 
-above step, you could do something like:
-
-  Given /^"(\w+)" is the father of "(\w+)"$/ do |father, child|
-    Fatherhood.create! :father => model!("person: \"#{father}\""), :child => model!("person: \"#{child}\"")
-  end 
-
-"Given <b>n models</b> exist", e.g.
-
-  Given 10 users exist
-
-"Given <b>n models</b> exist with <b>fields</b>", examples:
-
-  Given 10 users exist with activated: false
-
-"Given the following <b>models</b> exist:", examples:
-
-  Given the following users exist
-    | name  | activated |
-    | Fred  | false     |
-    | Ethel | true      |
-
-===== Named machinist blueprints
-
-"Given <b> a <i>named</i> model</b> exists with <b>fields</b>"
-
-The latest version of pickle supports {named machinist blueprints}[http://github.com/notahat/machinist/commit/d6492e6927a8aa1819926e48b22377171fd20496].
-
-If you had the following blueprints:
-
-  User.blueprint do
-    name
-    email
-  end
-  
-  User.blueprint(:super_admin) do
-    role { "admin" }
-  end
-  
-  User.blueprint(:activated) do
-    activated { true }
-  end
-
-You could create a user with pickle by simply adding the name of the blueprint before the model:
-
-  Given a super admin user exists
-  And an activated user exists with name: "Fred"
-
-This is much nicer than having to set up common configurations in your steps all the time, and far more readable to boot.
-
-
-==== Then steps
-
-===== Asserting existence of models
-
-"Then <b>a model</b> should exist",  e.g.
-
-  Then a user should exist
-
-"Then <b>a model</b> should exist with <b>fields</b>", e.g.
-
-  Then a user: "fred" should exist with name: "Fred" # we can label the found user for later use
-
-You can use other models, booleans, numerics, and strings as fields
-
-  Then a person should exist with child: person "ethel"
-  Then a user should exist with activated: false
-  Then a user should exist with activated: true, email: "fred@gmail.com"
-
-"Then <b>n models</b> should exist", e.g.
-
-  Then 10 events should exist
-
-"Then <b>n models</b> should exist with <b>fields</b>", e.g.
-
-  Then 2 people should exist with father: person "fred"
-
-"Then the following <b>models</b> exist". This allows the creation of multiple models
-using a table syntax. Using a column with the singularized name of the model creates a referenceable model. E.g.
-
-  Then the following users exist:
-    | name   | activated |
-    | Freddy | false     |
-
-  Then the following users exist:
-    | user | name   | activated |
-    | Fred | Freddy | false     |
-
-===== Asserting associations
-
-One-to-one assocs: "Then <b>a model</b> should be <b>other model</b>'s <b>association</b>", e.g.
-
-  Then the person: "fred" should be person: "ethel"'s father
-
-Many-to-one assocs: "Then <b>a model</b> should be [in|one of] <b>other model</b>'s <b>association</b>", e.g.
-
-  Then the person: "ethel" should be one of person: "fred"'s children
-  Then the comment should be in the post's comments
-
-===== Asserting predicate methods
-
-"Then <b>a model</b> should [be|have] [a|an] <b>predicate</b>", e.g.
-
-  Then the user should have a status # => user.status.should be_present
-  Then the user should have a stale password # => user.should have_stale_password
-  Then the car: "batmobile" should be fast # => car.should be_fast
-
-"Then <b>a model</b> should not [be|have] [a|an] <b>predicate</b>", e.g.
-
-  Then person: "fred" should not be childless # => fred.should_not be_childless
-
-=== Regexps for use in your own steps
-
-By default you get some regexps available in the main namespace for use
-in creating your own steps: `capture_model`, `capture_fields`, and others (see lib/pickle.rb)
-
-(You can use any of the regexps that Pickle uses by using the Pickle.parser namespace, see
-Pickle::Parser::Matchers for the methods available)
-
-*capture_model*
-
-  Given /^#{capture_model} exists$/ do |model_name|
-    model(model_name).should_not == nil
-  end
-
-  Then /^I should be at the (.*?) page$/ |page|
-    if page =~ /#{capture_model}'s/
-      url_for(model($1))
-    else
-      # ...
-    end
-  end
-
-  Then /^#{capture_model} should be one of #{capture_model}'s posts$/ do |post, forum|
-    post = model!(post)
-    forum = model!(forum)
-    forum.posts.should include(post)
-  end
-
-*capture_fields*
-
-This is useful for setting attributes, and knows about pickle model names so that you
-can build up composite objects with ease
-
-  Given /^#{capture_model} exists with #{capture_fields}$/ do |model_name, fields|
-    create_model(model_name, fields)
-  end
-
-  # example of use
-  Given a user exists
-  And a post exists with author: the user # this step will assign the above user as :author on the post
-
-=== Email Steps
-
-When you run <tt>rails g pickle --email</tt> you get steps for handling email.
-
-The general pattern of use is to clear the email queue (if necessary), have your app perform something that sends emails, assert that emails have been delivered, then assert 
-those emails have particular properties.
-
-For example:
-
-  Background:
-    Given a user has signed up
-    And all emails have been delivered
-    And the user has signed in
-    
-  Scenario: User buys a fork
-    Given I am on the fork page
-    And I press "Buy Fork!"
-    Then 1 email should be delivered to the user
-    And the email should contain "You can haz Fork!"
-    When I follow the "my account" link in the email
-    Then I should be on the account page
-    
-    And 1 email should be delivered to "sales@example.com"
-    And the email should contain the user's page
-    And the email should contain "User can haz Fork!"
-    
-You can refer to emails that were found in the <tt>Then <i>n</i> emails should be delivered</tt> in the following ways:
-
-  the email (refers to last email)
-  the 1st email
-  the last email
-  email to: "joe@example.com"
-  email subject: "some subject"
-  email to: "joe@example.com", subject: "some subject"
-
-==== Map expressions to email addresses
-
-By default a step like
-
-  Then 2 emails should be delivered to the user "Ethel"
-
-Will look for the <tt>email</tt> attribute on the found model.  This is configurable in much the same way as
-page names for url paths.  Have a look at <tt>features/support/email.rb</tt> to add your own custom mappings.
-
-For example:
-
-  # in features/support/email.rb
-  when /^#{capture_model} sales team$/
-    model!($1).sales_email
-
-  # in a feature
-    Given a site exists
-    And someone buys something form the site
-    Then 1 email should be delivered to the site sales team
-    
-More detail on the emails steps follows:
-
-==== Given steps
-
-Clear the email queue, e.g.
-
-  Given all email has been delivered
-  Given all emails have been delivered
-
-==== When steps
-
-When <b>[I|they]</b> follow <b>[text_or_regex|the first link]</b> the email, e.g.
-
-  When I click the first link in the email
-  When I follow "http://example.com/pickle" in the email
-  When I follow "some link text" in the email
-
-==== Then steps
-
-Then <b>n</b> email(s) should be delivered to <b>address</b>, e.g.
-
-  Then 1 email should be delivered to joe@example.com
-
-Then <b>n</b> email(s) should be delivered with <b>fields</b>, e.g.
-
-  Then 2 emails should be delivered with subject: "Welcome to pickle"
-  Then 2 email should be delivered with to: "joe@example.com", from: "pickle@example.com"
-
-Then <b>fields</b> should be delivered to <b>address</b>, e.g.
-
-  Then subject: "Welcome to pickle" should be delivered to joe@example.com
-
-Then <b>fields</b> should be not delivered to <b>address</b>, e.g.
-
-  Then subject: "Welcome to pickle" should not be delivered to pickle@example.com
-
-Then <b>email</b> should have <b>fields</b>, e.g.
-
-  Then the email should have subject: "Welcome to pickle", from: "pickle@example.com"
-
-Then <b>email</b> should contain "<b>text</b>", e.g.
-
-  Then the email should contain "Thank you for choosing pickle"
-
-Then <b>email</b> should not contain "<b>text</b>", e.g.
-
-  Then the email should not contain "v1@gr@"
-
-Then <b>email</b> should link to "<b>href</b>", e.g.
-
-  Then the email should link to http://example.com/pickle
-
-Then show me the email(s), will open the email(s) in your browser (depends on OS X)
-
-  Then show me the email(s)
-
-== Run the tests
-
-To run the specs and features, you can start from the last known good set of gem dependencies in Gemfile.lock.development:
-
-  git clone http://github.com/ianwhite/pickle
-  cd pickle
-  cp Gemfile.lock.development Gemfile.lock
-  bundle
-
-To run the specs & features do:
-
-  bundle exec rake spec
-  bundle exec rake cucumber
-
-== Contributors
-
-The following people have made Pickle better:
-
-* {Jules Copeland}[http://github.com/julescopeland]
-* {David Padilla}[http://github.com/dabit]
-* {Ari Epstein}[http://github.com/aepstein]
-* {Jonathan Hinkle}[http://github.com/hynkle]
-* {Devin Walters and Nick Karpenske}[http://github.com/bendyworks]
-* {Marc Lee}[http://github.com/maleko]
-* {Sebastian Zuchmanski}[http://github.com/sebcioz]
-* {Paul Gideon Dann}[http://github.com/giddie]
-* {Tom Meier}[http://github.com/tommeier]
-* {Sean Hussey}[http://github.com/seanhussey]
-* Brian Rose & Kevin Olsen
-* {Christopher Darroch}[http://github.com/chrisdarroch]
-* {Szymon Nowak}[http://github.com/szimek]
-* {H.J. Blok}[http://github.com/hjblok]
-* {Daniel Neighman}[http://github.com/hassox]
-* {Josh Bassett}[http://github.com/nullobject]
-* {Nick Rutherford}[http://github.com/nruth]
-* {Tobi Knaup}[http://github.com/guenter]
-* {Michael MacDonald}[http://github.com/schlick]
-* {Michael Moen}[http://github.com/UnderpantsGnome]
-* {Myron Marston}[http://github.com/myronmarston]
-* {Stephan Hagemann}[http://github.com/xing]
-* {Chris Flipse}[http://github.com/cflipse]
-