spbtv_pickle 0.5.1

data/Rakefile

@@ -0,0 +1,20 @@
+$:.unshift File.expand_path('lib')
+
+# load given tasks file, reporting errors without failing
+def load_tasks(tasks)
+  load tasks
+rescue Exception => exception
+  $stderr << "** loading #{tasks.sub(File.expand_path('.'),'')} failed: "
+  case exception
+  when LoadError
+    $stderr << "to use, install the gems it requires\n"
+  else
+    $stderr << ([exception.message] + exception.backtrace[0..2]).join("\n    ") << "\n\n"
+  end
+end
+
+Dir["Rakefile.d/*.rake"].sort.each {|t| load_tasks t}
+
+task :default => :spec
+
+task :ci => ['rcov:verify', 'cucumber']

data/Rakefile.d/cucumber.rake

@@ -0,0 +1,27 @@
+require 'cucumber/rake/task'
+
+desc "Run features"
+Cucumber::Rake::Task.new(:cucumber => [:cucumber_test_app]) do |t|
+  t.cucumber_opts = ['--format', 'pretty', '--require', 'features']
+end
+
+desc "setup a rails app for running cucumber"
+file "cucumber_test_app" do
+  puts "** setting up cucumber test app **"
+  Rake::Task['cucumber:setup'].invoke
+end
+
+namespace :cucumber do
+  task :setup do
+    Bundler.with_clean_env do
+      gemfile = "cucumber_test_app/Gemfile"
+      rm_rf "cucumber_test_app"
+      sh "bundle exec rails new cucumber_test_app --skip-javascript --skip-sprockets"
+      sh "echo 'gem \"cucumber-rails\", :require => false' >> #{gemfile}"
+      sh "echo 'gem \"rspec-rails\", \"~>3.0\"' >> #{gemfile}"
+      sh "echo 'gem \"capybara\"' >> #{gemfile}"
+      sh "bundle install --gemfile=#{gemfile}"
+      sh "ln -s ../../.. cucumber_test_app/vendor/plugins/pickle"
+    end
+  end
+end

data/Rakefile.d/release.rake

@@ -0,0 +1,44 @@
+# tasks for building and releasing the software
+require 'git'
+require 'pickle/version'
+
+task :build do
+  system "gem build pickle.gemspec"
+end
+
+namespace :release do
+  task :rubygems => :pre do
+    system "gem push pickle-#{Pickle::VERSION}.gem"
+  end
+  
+  task :github => :pre do
+    tag = "v#{Pickle::VERSION}"
+    git = Git.open('.')
+    
+    if (git.tag(tag) rescue nil)
+      raise "** repo is already tagged with: #{tag}"
+    end
+    
+    git.add_tag(tag)
+    git.push('origin', tag)
+  end
+  
+  task :pre => [:spec, :cucumber, :build] do
+    git = Git.open('.')
+    
+    if File.exists?("Gemfile.lock") && File.read("Gemfile.lock") != File.read("Gemfile.lock.development")
+      cp "Gemfile.lock", "Gemfile.lock.development"
+      raise "** Gemfile.lock.development has been updated, please commit these changes."
+    end
+    
+    if (git.status.changed + git.status.added + git.status.deleted).any?
+      raise "** repo is not clean, try committing some files"
+    end
+    
+    if git.object('HEAD').sha != git.object('origin/master').sha
+      raise "** origin does not match HEAD, have you pushed?"
+    end
+  end
+  
+  task :all => ['release:github', 'release:rubygems']
+end

data/Rakefile.d/rspec.rake

@@ -0,0 +1,3 @@
+require 'rspec/core/rake_task'
+
+RSpec::Core::RakeTask.new(:spec)

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/autotest/discover.rb

@@ -0,0 +1,9 @@
+require 'autotest/bundler'
+
+Autotest.add_hook :initialize do |autotest|
+  %w{.git .DS_Store ._* vendor tmp email cucumber_test_app}.each do |exception|
+    autotest.add_exception(exception)
+  end
+end
+
+Autotest.add_discovery { "rspec2" }

data/features/app/app.rb

@@ -0,0 +1,128 @@
+# Routes
+Rails.application.routes.draw do
+  resources :spoons, :controller => 'default'
+  resources :forks, :controller => 'default' do
+    resources :tines, :controller => 'default' do
+      resources :comments, :controller => 'default'
+    end
+  end
+  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
+
+    create_table :knives, :force => true do |t|
+      t.string :name
+      t.boolean :sharp, :null => 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
+
+# Fabricator class
+class Knife < 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 Rails.application.routes.url_helpers
+  
+  # BC 2.1
+  self.view_paths = "#{File.dirname(__FILE__)}/views"
+  
+  def user_email(user)
+    @recipients  = user.email
+    @subject     = 'A user email'
+    @user = user
+    @path = user_path(user)
+  end
+  
+  def email(to, subject, body)
+    @recipients  = to
+    @subject     = subject
+    @body = body
+  end
+end

data/features/app/blueprints.rb

@@ -0,0 +1,6 @@
+# Blueprints
+require 'machinist/active_record'
+
+Spoon.blueprint do
+  name { "A Spoon" }
+end

data/features/app/fabricators.rb

@@ -0,0 +1,6 @@
+require 'fabrication'
+
+Fabricator(:knife) do
+  name 'David'
+  sharp true
+end

data/features/app/factories.rb

@@ -0,0 +1,25 @@
+# Factories
+require 'factory_girl'
+
+FactoryGirl.define do
+  sequence :fork_name do |n|
+    "fork %d04" % n
+  end
+
+  factory :fork do |f|
+    f.name { FactoryGirl.generate(:fork_name) }
+  end
+
+  factory :tine do |t|
+    t.association :fork
+  end
+
+  factory :rusty_tine, :class => Tine do |t|
+    t.association :fork
+    t.rusty true
+  end
+
+  factory :fancy_fork, :class => Fork do |t|
+    t.name { "Fancy " + FactoryGirl.generate(:fork_name) }
+  end
+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 with a link "example page" to the user's page 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 with a link "example page" to the user's page 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 with a link "example page" to the user's page 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 "rails g 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 "rails g pickle --paths -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 "rails g 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 "rails g pickle --paths --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 "rails g pickle --paths --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