jeweler 1.4.0 → 1.5.0.pre2

data/features/generator/git.feature

@@ -92,3 +92,11 @@ Feature: git support
     Then 'features/the-perfect-gem.feature' was checked in
     And 'features/support/env.rb' was checked in
     And 'features/step_definitions/the-perfect-gem_steps.rb' was checked in
+
+  Scenario: shindo
+    Given a working directory
+    And I have configured git sanely
+    When I generate a shindo project named 'the-perfect-gem' that is 'zomg, so good'
+
+    Then 'tests/tests_helper.rb' was checked in
+    And 'tests/the-perfect-gem_tests.rb' was checked in

data/features/generator/license.feature

@@ -3,9 +3,18 @@ Feature: generated license
   A user should be able to
   generate a default license
 
-  Scenario: copyright
+  Background:
     Given a working directory
+
+  Scenario: crediting user
+    Given I have configured git sanely
+    When I generate a project named 'the-perfect-gem' that is 'zomg, so good'
+
+    Then LICENSE credits 'foo'
+
+  Scenario: copyright in the current year
+    Given it is the year 2005
     And I have configured git sanely
     When I generate a project named 'the-perfect-gem' that is 'zomg, so good'
 
-    Then LICENSE has the copyright as belonging to 'foo' in '2009'
+    Then LICENSE has a copyright in the year 2005

data/features/generator/rakefile.feature

@@ -10,7 +10,9 @@ Feature: generated Rakefile
   Scenario: shared
     When I generate a project named 'the-perfect-gem' that is 'zomg, so good' and described as 'Descriptive'
 
-    Then 'Rakefile' requires 'rubygems'
+    Then 'Rakefile' requires 'bundler'
+    And 'Rakefile' sets up bundler using the default and development groups
+    And 'Rakefile' requires 'rubygems'
     And 'Rakefile' requires 'rake'
     And 'Rakefile' requires 'rake/rdoctask'
     And Rakefile has 'the-perfect-gem' for the Jeweler::Tasks name
@@ -18,11 +20,10 @@ Feature: generated Rakefile
     And Rakefile has 'zomg, so good' for the Jeweler::Tasks summary
     And Rakefile has 'Descriptive' for the Jeweler::Tasks description
     And Rakefile has 'http://github.com/technicalpickles/the-perfect-gem' for the Jeweler::Tasks homepage
+    And Rakefile instantiates a Jeweler::GemcutterTasks
 
   Scenario: bacon
     When I generate a bacon project named 'the-perfect-gem' that is 'zomg, so good'
-
-
     Then 'Rakefile' requires 'rcov/rcovtask'
     And Rakefile has 'spec/**/*_spec.rb' for the Rake::TestTask pattern
     And Rakefile has 'spec/**/*_spec.rb' for the Rcov::RcovTask pattern
@@ -38,11 +39,13 @@ Feature: generated Rakefile
     And Rakefile has 'test' in the Rcov::RcovTask libs
     And Rakefile has "test" as the default task
 
+  @rspec
   Scenario: rspec
     When I generate a rspec project named 'the-perfect-gem' that is 'zomg, so good'
 
-    Then 'Rakefile' requires 'spec/rake/spectask'
-    And Rakefile has 'spec/**/*_spec.rb' for the Spec::Rake::SpecTask pattern
+    Then 'Rakefile' requires 'rspec/core'
+    And 'Rakefile' requires 'rspec/core/rake_task'
+    And Rakefile has 'spec/**/*_spec.rb' for the RSpec::Core::RakeTask pattern
     And Rakefile has "spec" as the default task
 
   Scenario: shoulda
@@ -113,11 +116,6 @@ Feature: generated Rakefile
     When I generate a testunit project named 'the-perfect-gem' that is 'zomg, so good'
     Then Rakefile does not instantiate a Jeweler::RubyforgeTasks
 
-  Scenario: rubyforge
-    Given I want rubyforge setup
-    When I generate a testunit project named 'the-perfect-gem' that is 'zomg, so good'
-    Then Rakefile instantiates a Jeweler::RubyforgeTasks
-
   Scenario: yard
     Given I want to use yard instead of rdoc
     When I generate a testunit project named 'the-perfect-gem' that is 'zomg, so good'
@@ -135,17 +133,21 @@ Feature: generated Rakefile
     And Rakefile does not instantiate a YARD::Rake::YardocTask
     And Rakefile instantiates a Rake::RDocTask.new
 
-  Scenario: rubyforge and yard
-    Given I want to use yard instead of rdoc
-    And I want rubyforge setup
-    When I generate a testunit project named 'the-perfect-gem' that is 'zomg, so good'
-    Then Rakefile instantiates a Jeweler::RubyforgeTasks
-    And Rakefile has 'yardoc' for the Jeweler::RubyforgeTasks doc_task
+  Scenario: shindo
+    When I generate a shindo project named 'the-perfect-gem' that is 'zomg, so good'
+    And 'Rakefile' requires 'shindo/rake'
+    And Rakefile instantiates a Shindo::Rake.new
+    And Rakefile has "tests" as the default task
 
-  Scenario: rubyfoge and doc
-    Given I want to use rdoc instead of yard
-    And I want rubyforge setup
-    And I want rubyforge setup
-    When I generate a testunit project named 'the-perfect-gem' that is 'zomg, so good'
-    Then Rakefile instantiates a Jeweler::RubyforgeTasks
-    And Rakefile has 'rdoc' for the Jeweler::RubyforgeTasks doc_task
+
+  Scenario: bundler
+    Given I want bundler
+    When I generate a project named 'the-perfect-gem' that is 'zomg, so good' and described as 'Descriptive'
+    Then 'Rakefile' requires 'bundler'
+    And 'Rakefile' sets up bundler using the default and development groups
+
+  Scenario: no bundler
+    Given I do not want bundler
+    When I generate a project named 'the-perfect-gem' that is 'zomg, so good' and described as 'Descriptive'
+    Then 'Rakefile' does not require 'bundler'
+    And 'Rakefile' does not setup bundler

data/features/generator/test.feature

@@ -46,3 +46,9 @@ Feature: generated test or spec
     When I generate a riot project named 'the-perfect-gem' that is 'zomg, so good'
     Then 'test/the-perfect-gem_test.rb' should contextualize 'the-perfect-gem'
       And 'test/the-perfect-gem_test.rb' requires 'teststrap'
+
+  Scenario: shindo
+    Given a working directory
+    And I have configured git sanely
+    When I generate a shindo project named 'the-perfect-gem' that is 'zomg, so good'
+    Then 'tests/the-perfect-gem_tests.rb' should have tests for 'ThePerfectGem'

data/features/generator/test_helper.feature

@@ -3,54 +3,150 @@ Feature: generated test or spec
   A user should be able to
   generate a test or spec
 
-  Scenario: bacon
+  Scenario: bacon w/ bundler
     Given a working directory
     And I have configured git sanely
+    And I want bundler
     When I generate a bacon project named 'the-perfect-gem' that is 'zomg, so good'
-    Then 'spec/spec_helper.rb' requires 'bacon'
+    Then 'spec/spec_helper.rb' requires 'bundler'
+    And 'spec/spec_helper.rb' sets up bundler using the default and development groups
+    And 'spec/spec_helper.rb' requires 'bacon'
     And 'spec/spec_helper.rb' requires 'the-perfect-gem'
 
-  Scenario: minitest
+  Scenario: bacon w/o bundler
     Given a working directory
     And I have configured git sanely
+    And I do not want bundler
+    When I generate a bacon project named 'the-perfect-gem' that is 'zomg, so good'
+    Then 'spec/spec_helper.rb' does not require 'bundler'
+    And 'spec/spec_helper.rb' does not setup bundler
+
+  Scenario: minitest w/ bundler
+    Given a working directory
+    And I have configured git sanely
+    And I want bundler
     When I generate a minitest project named 'the-perfect-gem' that is 'zomg, so good'
-    Then 'test/helper.rb' requires 'minitest/unit'
+    Then 'test/helper.rb' requires 'bundler'
+    And 'test/helper.rb' sets up bundler using the default and development groups
+    And 'test/helper.rb' requires 'minitest/unit'
     And 'test/helper.rb' requires 'the-perfect-gem'
     And 'test/helper.rb' should autorun tests
 
-  Scenario: rspec
+  Scenario: minitest w/o bundler
     Given a working directory
     And I have configured git sanely
+    And I do not want bundler
+    When I generate a minitest project named 'the-perfect-gem' that is 'zomg, so good'
+    Then 'test/helper.rb' does not require 'bundler'
+    And 'test/helper.rb' does not setup bundler
+
+  Scenario: rspec w/ bundler
+    Given a working directory
+    And I have configured git sanely
+    And I want bundler
     When I generate a rspec project named 'the-perfect-gem' that is 'zomg, so good'
-    Then 'spec/spec_helper.rb' requires 'spec'
+    Then 'spec/spec_helper.rb' requires 'bundler'
+    And 'spec/spec_helper.rb' sets up bundler using the default and development groups
+    And 'spec/spec_helper.rb' requires 'rspec'
+    And 'spec/spec_helper.rb' requires 'rspec/autorun'
     And 'spec/spec_helper.rb' requires 'the-perfect-gem'
 
-  Scenario: shoulda
+  Scenario: rspec w/o bundler
+    Given a working directory
+    And I have configured git sanely
+    And I do not want bundler
+    When I generate a rspec project named 'the-perfect-gem' that is 'zomg, so good'
+    Then 'spec/spec_helper.rb' does not require 'bundler'
+    And 'spec/spec_helper.rb' does not setup bundler
+
+  Scenario: shoulda w/ bundler
     Given a working directory
     And I have configured git sanely
+    And I want bundler
     When I generate a shoulda project named 'the-perfect-gem' that is 'zomg, so good'
-    Then 'test/helper.rb' requires 'test/unit'
+    Then 'test/helper.rb' requires 'bundler'
+    And 'test/helper.rb' sets up bundler using the default and development groups
+    And 'test/helper.rb' requires 'test/unit'
     And 'test/helper.rb' requires 'shoulda'
     And 'test/helper.rb' requires 'the-perfect-gem'
 
-  Scenario: testunit
+  Scenario: shoulda w/o bundler
     Given a working directory
     And I have configured git sanely
+    And I do not want bundler
+    When I generate a shoulda project named 'the-perfect-gem' that is 'zomg, so good'
+    And 'test/helper.rb' does not require 'bundler'
+    And 'test/helper.rb' does not setup bundler
+
+  Scenario: testunit w/ bundler
+    Given a working directory
+    And I have configured git sanely
+    And I want bundler
     When I generate a testunit project named 'the-perfect-gem' that is 'zomg, so good'
     Then 'test/helper.rb' requires 'test/unit'
     And 'test/helper.rb' requires 'the-perfect-gem'
+    And 'test/helper.rb' requires 'bundler'
+    And 'test/helper.rb' sets up bundler using the default and development groups
 
-  Scenario: micronaut
+  Scenario: testunit w/o bundler
     Given a working directory
     And I have configured git sanely
+    And I do not want bundler
+    When I generate a testunit project named 'the-perfect-gem' that is 'zomg, so good'
+    And 'test/helper.rb' does not require 'bundler'
+    And 'test/helper.rb' does not setup bundler
+
+  Scenario: micronaut w/ bundler
+    Given a working directory
+    And I have configured git sanely
+    And I want bundler
     When I generate a micronaut project named 'the-perfect-gem' that is 'zomg, so good'
     Then 'examples/example_helper.rb' requires 'rubygems'
     Then 'examples/example_helper.rb' requires 'micronaut'
     Then 'examples/example_helper.rb' requires 'the-perfect-gem'
+    And 'examples/example_helper.rb' requires 'bundler'
+    And 'examples/example_helper.rb' sets up bundler using the default and development groups
 
-  Scenario: riot
+  Scenario: micronaut w/o bundler
+    Given a working directory
+    And I have configured git sanely
+    And I do not want bundler
+    When I generate a micronaut project named 'the-perfect-gem' that is 'zomg, so good'
+    And 'examples/example_helper.rb' does not require 'bundler'
+    And 'examples/example_helper.rb' does not setup bundler
+
+  Scenario: riot w/ bundler
     Given a working directory
       And I have configured git sanely
+      And I want bundler
     When I generate a riot project named 'the-perfect-gem' that is 'zomg, so good'
     Then 'test/teststrap.rb' requires 'riot'
       And 'test/teststrap.rb' requires 'the-perfect-gem'
+      And 'test/teststrap.rb' requires 'bundler'
+      And 'test/teststrap.rb' sets up bundler using the default and development groups
+
+  Scenario: riot w/o bundler
+    Given a working directory
+      And I have configured git sanely
+      And I do not want bundler
+    When I generate a riot project named 'the-perfect-gem' that is 'zomg, so good'
+      And 'test/teststrap.rb' does not require 'bundler'
+      And 'test/teststrap.rb' does not setup bundler
+
+  Scenario: shindo w/ bundler
+    Given a working directory
+    And I have configured git sanely
+    And I want bundler
+    When I generate a shindo project named 'the-perfect-gem' that is 'zomg, so good'
+    Then 'tests/tests_helper.rb' requires 'the-perfect-gem'
+    Then 'tests/tests_helper.rb' requires 'shindo'
+    Then 'tests/tests_helper.rb' requires 'bundler'
+    And 'tests/tests_helper.rb' sets up bundler using the default and development groups
+
+  Scenario: shindo w/o bundler
+    Given a working directory
+    And I have configured git sanely
+    And I do not want bundler
+    When I generate a shindo project named 'the-perfect-gem' that is 'zomg, so good'
+    Then 'tests/tests_helper.rb' does not require 'bundler'
+    And 'tests/tests_helper.rb' does not setup bundler

data/features/step_definitions/filesystem_steps.rb

@@ -1,7 +1,9 @@
 Given 'a working directory' do
-  @working_dir = File.expand_path File.join(File.dirname(__FILE__), '..', '..', 'tmp')
-  FileUtils.rm_rf @working_dir
-  FileUtils.mkdir_p @working_dir
+  @working_dir = create_construct
+end
+
+After do
+  @working_dir.destroy! if @working_dir
 end
 
 Given /^I use the jeweler command to generate the "([^"]+)" project in the working directory$/ do |name|

data/features/step_definitions/generator_steps.rb

@@ -14,6 +14,15 @@ Given /^I want reek$/ do
   @use_reek = true
 end
 
+Given /^I do not want bundler$/ do
+  @use_bundler = false
+end
+
+
+Given /^I want bundler$/ do
+  @use_bundler = true
+end
+
 Given /^I do not want roodi$/ do
   @use_roodi = false
 end
@@ -86,9 +95,15 @@ When /^I generate a (.*)project named '((?:\w|-|_)+)' that is '([^']*)' and desc
                 @use_rubyforge ? '--rubyforge' : nil,
                 @use_roodi ? '--roodi' : nil,
                 @use_reek ? '--reek' : nil,
+                case @use_bundler
+                when true then '--bundler'
+                when false then '--no-bundler'
+                else nil
+                end,
                 @documentation_framework ? "--#{@documentation_framework}" : nil,
                 @name].compact
 
+
   @stdout = OutputCatcher.catch_out do
     Jeweler::Generator::Application.run! *arguments
   end
@@ -170,16 +185,25 @@ Then /^'(.*)' mentions copyright belonging to me in the current year$/ do |file|
 end
 
 
-Then /^LICENSE has the copyright as belonging to '(.*)' in '(\d{4})'$/ do |copyright_holder, year|
+Then /^LICENSE credits '(.*)'$/ do |copyright_holder|
   Then "a file named 'the-perfect-gem/LICENSE' is created"
-
   @license_content ||= File.read(File.join(@working_dir, @name, 'LICENSE'))
-
   assert_match copyright_holder, @license_content
+end
 
+Given /^it is the year (\d+)$/ do |year|
+  time = Time.local(year.to_i, 9, 1, 10, 5, 0)
+  Timecop.travel(time)
+end
+
+
+Then /^LICENSE has a copyright in the year (\d+)$/ do |year|
+  Then "a file named 'the-perfect-gem/LICENSE' is created"
+  @license_content ||= File.read(File.join(@working_dir, @name, 'LICENSE'))
   assert_match year, @license_content
 end
 
+
 Then /^'(.*)' should define '(.*)' as a subclass of '(.*)'$/ do |file, class_name, superclass_name|
   @test_content = File.read((File.join(@working_dir, @name, file)))
 
@@ -198,6 +222,12 @@ Then /^'(.*)' should contextualize '(.*)'$/ do |file, describe_name|
   assert_match %Q{context "#{describe_name}" do}, @spec_content
 end
 
+Then /^'(.*)' should have tests for '(.*)'$/ do |file, describe_name|
+  @tests_content ||= File.read((File.join(@working_dir, @name, file)))
+
+  assert_match %Q{Shindo.tests("#{describe_name}") do}, @tests_content
+end
+
 Then /^'(.*)' requires '(.*)'$/ do |file, lib|
   content = File.read(File.join(@working_dir, @name, file))
 
@@ -287,5 +317,39 @@ end
 
 After do
   ENV['JEWELER_OPTS'] = nil
-  FileUtils.rm_rf @working_dir if @working_dir
 end
+
+Then /^'Gemfile' has a (\w+) dependency on '(.*)'$/ do |group, name|
+  @gemfile_content ||= File.read(File.join(@working_dir, @name, 'Gemfile'))
+
+  group_block = yank_group_info(@gemfile_content, group)
+
+  assert_match name, group_block
+end
+
+Then /^'Gemfile' has a development dependency on the current version of jeweler$/ do
+  @gemfile_content ||= File.read(File.join(@working_dir, @name, 'Gemfile'))
+  group_block = yank_group_info(@gemfile_content, 'development')
+  
+  assert_match %Q{gem "jeweler", "~> #{Jeweler::Version::STRING}"}, group_block
+end
+
+
+Then /^'(.*)' sets up bundler using the default and development groups$/ do |file|
+  content = File.read(File.join(@working_dir, @name, file))
+
+  assert_match "Bundler.setup(:default, :development)", content
+end
+
+Then /^'(.*)' does not setup bundler$/ do |file|
+  content = File.read(File.join(@working_dir, @name, file))
+
+  assert_no_match /Bundler\.setup/, content
+end
+
+Then /^'Gemfile' uses the (.*) source$/ do |source|
+  content = File.read(File.join(@working_dir, @name, 'Gemfile'))
+
+  assert_match "source :#{source}", content
+end
+

data/features/support/env.rb

@@ -1,29 +1,42 @@
-$LOAD_PATH.unshift(File.dirname(__FILE__) + '/../../lib')
-require 'jeweler'
-
+require 'bundler'
 begin
-  require 'mocha'
-  require 'output_catcher'
-rescue LoadError => e
-  puts "*" * 80
-  puts "Some dependencies needed to run tests were missing. Run the following command to find them:"
-  puts
-  puts "\trake check_dependencies:development"
-  puts "*" * 80
-  exit 1
+  Bundler.setup(:default, :development)
+rescue Bundler::BundlerError => e
+  $stderr.puts e.message
+  $stderr.puts "Run `bundle install` to install missing gems"
+  exit e.status_code
 end
 
+$LOAD_PATH.unshift(File.dirname(__FILE__) + '/../../lib')
+require 'jeweler'
+require 'mocha'
+require 'output_catcher'
+require 'timecop'
+require 'ruby-debug'
+require 'active_support'
 
 require 'test/unit/assertions'
-
 World(Test::Unit::Assertions)
 
+require 'construct'
+World(Construct::Helpers)
+
 def yank_task_info(content, task)
   if content =~ /#{Regexp.escape(task)}.new(\(.*\))? do \|(.*?)\|(.*?)end/m
     [$2, $3]
   end
 end
 
+def yank_group_info(content, group)
+  if content =~ /group :#{group} do(.*?)end/m
+    $1
+  end
+end
+
 def fixture_dir
   File.expand_path File.join(File.dirname(__FILE__), '..', '..', 'test', 'fixtures')
 end
+
+After do
+  Timecop.return
+end