pickle 0.1.16

data/.gitignore

@@ -0,0 +1,2 @@
+doc/*
+.garlic

data/History.txt

@@ -0,0 +1,165 @@
+== 0.1.16 - 13 Oct 2009
+
+* 1 minor enhancement
+  * release gem on gemcutter and rubyforge
+
+
+== 0.1.15 - 28 Aug 2009
+
+* 1 minor enhancement
+	* avoid namespace collision on replace by renaming mapping#replace -> mapping#replacement [nruth]
+
+
+== 0.1.14 - 9 July 2009
+
+* 1 minor enhancement
+  * update specs and features for latest cucumber and machinist changes
+
+
+== 0.1.13 - 16 June 2009    
+
+* 2 minor enhancements
+  * model! and created_model! raise an error if pickle name can't be found
+  * path_to_pickle uses the above to give back a better error message
+
+
+== 0.1.12 - 7 Apr 2009
+
+* 2 minor enhancements
+  * rationalised Rakefile
+  * update World extensions for latest cucumber changes
+
+
+== 0.1.11 - 22 Feb 2009
+
+* 2 minor enhancements
+  * Pickle now supports multiple machinist blueprints
+  * Fix confusing adapter/adaptor comment generator comment 
+
+
+== 0.1.10 - 13 Feb 2009
+
+* 2 minor enhancements
+  * Made pickle paths generator compatible with latest cucumber
+  * Simplified and Rakefile, including auto push api docs to gh-pages on ci build
+
+
+== 0.1.9 - 29 Jan 2009
+
+* 1 minor enhancement
+  * Pickle::Adapter.model_classes excludes those without tables
+
+
+== 0.1.8 - 29 Jan 2009
+
+* API change
+  * pickle_path becomes path_to_pickle, to avoid named route clashes
+
+* 2 minor enhancements
+  * Updated features for cucumber 0.2 compat
+  * Made paths allow for optional possesives
+
+
+== 0,1,7
+
+* 2 API changes
+  * script/generate pickle path[s] now amends the features/support/paths.rb file
+    instead of creating pge_to_path and path_steps.
+    
+  * pickle_email_steps is renamed email_steps
+
+
+== 0.1.6
+
+* 1 API change
+  * to use pickle env.rb should contain "require 'pickle/world'".  You should remove all trace of
+    pickle from features/support/env.rb and re run script/generate pickle
+
+* 2 major enhancements
+
+  * generate email steps with `script/generate pickle email`
+    email steps allow you to do things like this:
+    
+      Then 2 emails should be delivered
+      And the first email should be delivered to fred@gmail.com
+      And the 2nd email should be delivered to the user: "ethel"
+      
+      Then 1 email should be delivered with subject: "Activate your account"
+      And the email should link to the user's page
+    
+    take a look at features/step_definitions/pickle_email_steps.rb
+      
+  * generate path steps with `script/generate pickle path`
+    path steps allow you to do things like this
+    
+      When I go to the comment's page
+      Then I should be at the user's new comment page
+    
+    take a look at features/step_definitions/pickle_path_steps.rb, and modify page_to_path to suit your needs
+
+* 4 minor enhancements
+  * Improved documentation
+  * abstract models no longer kill pickle
+  * Actually test that the generators work
+  * Made Pickle::Session a plain ole mixin, as a separate class was unnecessary
+  * Pickle uses the cucumber World API
+
+
+== 0.1.5
+
+* API change
+  * CaptureModel, etc are now 'capture_model' methods
+
+* 3 major enhancements
+  * Steps for asserting that <n> models exist, matching certain criteria
+  * Steps for asserting associations added to generated pickle steps
+      'Then the user should be in the post's commenters'
+      'Then the forum: "awesome" should be the 2nd post's forum'
+  * configuration can now occur any time before a step is defined, which makes
+    for much more intuitive env.rb
+
+* 2 minor enhancement
+  * predicate matching is less prone to step conflicts because we preload a 
+    big list of all the predicate and column methods
+  * field values now handle booleans and numerics
+
+
+== 0.1.4
+
+* 1 major enhancement
+  * You can create multiple models with ease, for eg.
+      'Given 10 users exist with role: "admin"'
+
+* 1 minor enhancement
+  * You can do Pickle.configure (just like Webrat.configure)
+
+
+== 0.1.3 - Bugfix release
+
+* 1 minor enhancement
+  * make generated steps compatible with Rails 2.1
+
+
+== 0.1.2
+
+* 2 major enhancements
+  * create your pickle steps with script/generate pickle
+  * Adapter based architecture, supports Machinist, FactoryGirl, and vanilla ActiveRecord
+  
+* 1 minor enhancement
+  * model_names now defaults to subclasses of AR::Base
+  * #original_model => #created_model
+
+
+== 0.1.1
+
+* 1 major enhancement:
+  * made pickle a github gem
+
+* 1 minor enhancement:
+  * Added intentions for pickle in README.textile
+
+
+== Prior to gems
+
+* Initial release: everything is subject to sweeping change

data/License.txt

@@ -0,0 +1,20 @@
+Copyright (c) 2008-2009 Ian White - ian.w.white@gmail.com
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/README.rdoc

@@ -0,0 +1,205 @@
+= pickle
+
+Pickle gives you cucumber steps that create your models easily from factory-girl or
+machinist factories/blueprints.  You can also just use ActiveRecord but it's not as cool.
+
+References to the models are stored, 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
+
+== CI
+
+It's tested against all stable branches of 2.x rails, and edge, with the latest versions of rspec, cucumber, factory_girl, machinist.
+
+== Install
+
+Install pickle either as a rails plugin, or a gem
+
+  # gem form rubyforge or gemcutter
+  sudo gem install pickle
+
+  # plugin
+  script/plugin install git://github.com/ianwhite/pickle.git
+  
+  # or, plugin as submodule
+  git submodule add git://github.com/ianwhite/pickle.git vendor/plugins/pickle
+
+  # or, github gem
+  sudo gem install ianwhite-pickle
+  
+== Get Started
+
+(you'd better install cucumber)
+
+  script/generate pickle [paths] [email]
+
+Now have a look at <tt>features/step_definitions/pickle_steps.rb</tt>
+
+If you want path steps and email steps then just add 'paths' and/or 'email'.  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
+
+If you have an AR 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
+
+==== Machinst: require your blueprints and reset Shams
+
+(The latest version of pickle supports {multiple blueprints}[http://github.com/notahat/machinist/commit/d6492e6927a8aa1819926e48b22377171fd20496], for 
+earlier versions of machinist use pickle <= 0.1.10)
+
+In your <tt>features/support/env.rb</tt> add the following lines at the bottom
+
+  require "#{Rails.root}/spec/blueprints" # or wherever they live
+  Before { Sham.reset } # reset Shams in between scenarios
+
+=== 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 
+
+  require 'pickle/world'
+
+  Pickle.configure do |config|
+    config.adapters = [:machinist, YourOwnAdapterClass]
+    config.map 'me', 'myself', 'my', 'I', :to => 'user: "me"'
+  end
+
+== 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
+  
+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: user "fred", child: user "ethel"
+  
+"Given <b>n</b> models exist", e.g.
+  
+  Given 10 users exist
+  
+"Given <b>n</b> <b>models</b> exist with <b>fields</b>", examples:
+
+  Given 10 users exist with activated: false
+
+==== 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</b> <b>models</b> should exist", e.g.
+
+  Then 10 events should exist
+  
+"Then <b>n</b> <b>models</b> should exist with <b>fields</b>", e.g.
+
+  Then 2 people should exist with father: person "fred"
+  
+===== 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 == true
+  Then the car: "batmobile" should be fast # => car.fast?.should == true
+  
+"Then <b>a model</b> should [be|have] [a|an] <b>predicate</b>", e.g.
+
+  Then person: "fred" should not be childless # => fred.childless?.should == false
+  
+=== 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|
+    model(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

data/Rakefile

@@ -0,0 +1,116 @@
+# use pluginized rpsec if it exists
+rspec_base = File.expand_path(File.dirname(__FILE__) + '/../rspec/lib')
+$LOAD_PATH.unshift(rspec_base) if File.exist?(rspec_base) and !$LOAD_PATH.include?(rspec_base)
+
+require 'spec/rake/spectask'
+require 'spec/rake/verify_rcov'
+
+$LOAD_PATH.unshift File.dirname(__FILE__) + '/lib'
+require 'pickle/version'
+
+PluginName = 'pickle'
+
+task :default => [:spec]
+
+desc "Run the specs for #{PluginName}"
+Spec::Rake::SpecTask.new(:spec) do |t|
+  t.spec_files = FileList['spec/**/*_spec.rb']
+  t.spec_opts  = ["--colour"]
+end
+
+desc "Generate RCov report for #{PluginName}"
+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', "spec/,rcov.rb,#{File.expand_path(File.join(File.dirname(__FILE__),'../../..'))}"] 
+end
+
+namespace :rcov do
+  desc "Verify RCov threshold for #{PluginName}"
+  RCov::VerifyTask.new(:verify => :rcov) do |t|
+    t.threshold = 100.0
+    t.index_html = File.join(File.dirname(__FILE__), 'doc/coverage/index.html')
+  end
+end
+
+# cucumber features require an enclosing rails app
+plugins_base = File.expand_path(File.join(File.dirname(__FILE__), '..'))
+cucumber_base = File.join(plugins_base, 'cucumber/lib')
+if File.exists?(cucumber_base) && plugins_base =~ /\/vendor\/plugins$/ # if we're in rails app
+  $:.unshift(cucumber_base)
+  require 'cucumber/rake/task'
+
+  desc "Run features for #{PluginName} (progress)"
+  Cucumber::Rake::Task.new(:features) do |t|
+    t.fork = true
+    t.cucumber_opts = ['--format', 'progress', '--require', 'features']
+  end
+  
+  desc "Run features for #{PluginName} (full output)"
+  namespace :features do
+    Cucumber::Rake::Task.new(:full) do |t|
+      t.cucumber_opts = ['--format', 'pretty', '--require', 'features']
+    end
+  end
+end
+
+# the following optional tasks are for CI, gems and doc building
+begin
+  require 'hanna/rdoctask'
+  require 'garlic/tasks'
+  require 'grancher/task'
+  
+  task :cruise => ['garlic:all', 'doc:publish']
+  
+  Rake::RDocTask.new(:doc) do |d|
+    d.options << '--all'
+    d.rdoc_dir = 'doc'
+    d.main     = 'README.rdoc'
+    d.title    = "#{PluginName} API docs"
+    d.rdoc_files.include('README.rdoc', 'History.txt', 'License.txt', 'Todo.txt', 'lib/**/*.rb')
+  end
+
+  namespace :doc do
+    task :publish => :doc do
+      Rake::Task['doc:push'].invoke unless uptodate?('.git/refs/heads/gh-pages', 'doc')
+    end
+    
+    Grancher::Task.new(:push) do |g|
+      g.keep_all
+      g.directory 'doc', 'doc'
+      g.branch = 'gh-pages'
+      g.push_to = 'origin'
+    end
+  end
+rescue LoadError
+end
+
+begin
+  require 'jeweler'
+  
+  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"]
+    s.rubyforge_project = 'pickle'
+  end
+
+  Jeweler::GemcutterTasks.new
+
+  Jeweler::RubyforgeTasks.new do |rubyforge|
+    rubyforge.doc_task = "doc"
+  end
+
+  namespace :release do
+    desc "Release current version to github, gemcutter and rubyforge"
+    task :all => ['release', 'gemcutter:release', 'rubyforge:release']
+  end
+
+rescue LoadError
+  puts "Jeweler not available for gem tasks. Install it with: sudo gem install jeweler"
+end