gemrage 0.0.0

data/vendor/ruby/1.8/gems/jeweler-1.4.0/features/generator/cucumber.feature

@@ -0,0 +1,83 @@
+Feature: generating cucumber stories
+  In order to get started using cucumber in a project
+  A user should be able to
+  generate a project setup for their testing framework of choice
+
+  Scenario: sans cucumber setup
+    Given a working directory
+    And I have configured git sanely
+    And I do not want cucumber stories
+    When I generate a project named 'the-perfect-gem' that is 'zomg, so good'
+
+    And a file named 'the-perfect-gem/features/the-perfect-gem.feature' is not created
+    And a file named 'the-perfect-gem/features/support/env.rb' is not created
+    And a file named 'the-perfect-gem/features/steps/the-perfect-gem_steps.rb' is not created
+
+  Scenario: basic cucumber setup
+    Given a working directory
+    And I have configured git sanely
+    And I want cucumber stories
+    When I generate a project named 'the-perfect-gem' that is 'zomg, so good'
+
+    Then cucumber directories are created
+
+    And a file named 'the-perfect-gem/features/the-perfect-gem.feature' is created
+    And a file named 'the-perfect-gem/features/support/env.rb' is created
+    And a file named 'the-perfect-gem/features/step_definitions/the-perfect-gem_steps.rb' is created
+
+    And 'features/support/env.rb' requires 'the-perfect-gem'
+
+  Scenario: cucumber setup for bacon
+    Given a working directory
+    And I have configured git sanely
+    And I want cucumber stories
+    When I generate a bacon project named 'the-perfect-gem' that is 'zomg, so good'
+
+    Then 'features/support/env.rb' requires 'test/unit/assertions'
+    And cucumber world extends "Test::Unit::Assertions"
+
+  Scenario: cucumber setup for shoulda
+    Given a working directory
+    And I have configured git sanely
+    And I want cucumber stories
+    When I generate a shoulda project named 'the-perfect-gem' that is 'zomg, so good'
+
+    Then 'features/support/env.rb' requires 'test/unit/assertions'
+    And cucumber world extends "Test::Unit::Assertions"
+
+  Scenario: cucumber setup for testunit
+    Given a working directory
+    And I have configured git sanely
+    And I want cucumber stories
+    When I generate a testunit project named 'the-perfect-gem' that is 'zomg, so good'
+
+    Then 'features/support/env.rb' requires 'test/unit/assertions'
+    And cucumber world extends "Test::Unit::Assertions"
+
+  Scenario: cucumber setup for minitest
+    Given a working directory
+    And I have configured git sanely
+    And I want cucumber stories
+    When I generate a minitest project named 'the-perfect-gem' that is 'zomg, so good'
+
+    Then 'features/support/env.rb' requires 'minitest/unit'
+    And cucumber world extends "MiniTest::Assertions"
+
+  Scenario: cucumber setup for rspec
+    Given a working directory
+    And I have configured git sanely
+    And I want cucumber stories
+    When I generate a rspec project named 'the-perfect-gem' that is 'zomg, so good'
+
+    Then 'features/support/env.rb' requires 'the-perfect-gem'
+    And 'features/support/env.rb' requires 'spec/expectations'
+
+  Scenario: cucumber setup for mirconaut
+    Given a working directory
+    And I have configured git sanely
+    And I want cucumber stories
+    When I generate a micronaut project named 'the-perfect-gem' that is 'zomg, so good'
+
+    Then 'features/support/env.rb' requires 'the-perfect-gem'
+    And 'features/support/env.rb' requires 'micronaut/expectations'
+    And cucumber world extends "Micronaut::Matchers"

data/vendor/ruby/1.8/gems/jeweler-1.4.0/features/generator/directory_layout.feature

@@ -0,0 +1,76 @@
+Feature: generated directory layout
+  In order to start a new gem
+  A user should be able to
+  generate a directory layout
+
+  Scenario: shared
+    Given a working directory
+    And I have configured git sanely
+    When I generate a project named 'the-perfect-gem' that is 'zomg, so good'
+
+    Then a directory named 'the-perfect-gem' is created
+    And a directory named 'the-perfect-gem/lib' is created
+
+    And a file named 'the-perfect-gem/README.rdoc' is created
+    And a file named 'the-perfect-gem/.document' is created
+    And a file named 'the-perfect-gem/lib/the-perfect-gem.rb' is created
+
+  Scenario: bacon
+    Given a working directory
+    And I have configured git sanely
+    When I generate a bacon project named 'the-perfect-gem' that is 'zomg, so good'
+
+    Then a directory named 'the-perfect-gem/spec' is created
+
+    And a file named 'the-perfect-gem/spec/spec_helper.rb' is created
+    And a file named 'the-perfect-gem/spec/the-perfect-gem_spec.rb' is created
+
+  Scenario: minitest
+    Given a working directory
+    And I have configured git sanely
+    When I generate a minitest project named 'the-perfect-gem' that is 'zomg, so good'
+
+    Then a directory named 'the-perfect-gem/test' is created
+
+    And a file named 'the-perfect-gem/test/helper.rb' is created
+    And a file named 'the-perfect-gem/test/test_the-perfect-gem.rb' is created
+
+  Scenario: rspec
+    Given a working directory
+    And I have configured git sanely
+    When I generate a rspec project named 'the-perfect-gem' that is 'zomg, so good'
+
+    Then a directory named 'the-perfect-gem/spec' is created
+
+    And a file named 'the-perfect-gem/spec/spec_helper.rb' is created
+    And a file named 'the-perfect-gem/spec/the-perfect-gem_spec.rb' is created
+
+  Scenario: shoulda
+    Given a working directory
+    And I have configured git sanely
+    When I generate a shoulda project named 'the-perfect-gem' that is 'zomg, so good'
+
+    Then a directory named 'the-perfect-gem/test' is created
+
+    And a file named 'the-perfect-gem/test/helper.rb' is created
+    And a file named 'the-perfect-gem/test/test_the-perfect-gem.rb' is created
+
+  Scenario: testunit
+    Given a working directory
+    And I have configured git sanely
+    When I generate a testunit project named 'the-perfect-gem' that is 'zomg, so good'
+
+    Then a directory named 'the-perfect-gem/test' is created
+
+    And a file named 'the-perfect-gem/test/helper.rb' is created
+    And a file named 'the-perfect-gem/test/test_the-perfect-gem.rb' is created
+
+  Scenario: micronaut
+    Given a working directory
+    And I have configured git sanely
+    When I generate a micronaut project named 'the-perfect-gem' that is 'zomg, so good'
+
+    Then a directory named 'the-perfect-gem/examples' is created
+
+    And a file named 'the-perfect-gem/examples/example_helper.rb' is created
+    And a file named 'the-perfect-gem/examples/the-perfect-gem_example.rb' is created

data/vendor/ruby/1.8/gems/jeweler-1.4.0/features/generator/dotdocument.feature

@@ -0,0 +1,14 @@
+Feature: generated .document
+  In order to easily generate RDoc
+  A user should be able to
+  generate reasonable .document file
+
+  Scenario: .document
+    Given a working directory
+    And I have configured git sanely
+    When I generate a project named 'the-perfect-gem' that is 'zomg, so good'
+    Then '.document' contains 'README.rdoc'
+    And '.document' contains 'lib/**/*.rb'
+    And '.document' contains 'bin/*'
+    And '.document' contains 'features/**/*.feature'
+    And '.document' contains 'LICENSE'

data/vendor/ruby/1.8/gems/jeweler-1.4.0/features/generator/env_options.feature

@@ -0,0 +1,9 @@
+Feature: Getting options from environment variable
+  In order to avoid having to type --rspec over and over
+  A user will need to set up a JEWELER_OPTS environment variable
+
+  Scenario: Environment variable set
+    Given a working directory
+    And I set JEWELER_OPTS env variable to "--rspec"
+    When I generate a project named 'the-perfect-gem' that is 'zomg, so good'
+    Then 'spec/the-perfect-gem_spec.rb' should describe 'ThePerfectGem'

data/vendor/ruby/1.8/gems/jeweler-1.4.0/features/generator/git.feature

@@ -0,0 +1,94 @@
+Feature: git support
+  In order to start a new gem for GitHub
+  A user should be able to
+  generate a project that is setup for git
+
+  Scenario: git remote configuration
+    Given a working directory
+    And I have configured git sanely
+    When I generate a project named 'the-perfect-gem' that is 'zomg, so good'
+
+    Then git repository has 'origin' remote
+    And git repository 'origin' remote should be 'git@github.com:technicalpickles/the-perfect-gem.git'
+
+  Scenario: .gitignore
+    Given a working directory
+    And I have configured git sanely
+    When I generate a project named 'the-perfect-gem' that is 'zomg, so good'
+
+    Then a sane '.gitignore' is created
+
+  Scenario: baseline repository
+    Given a working directory
+    And I have configured git sanely
+    When I generate a project named 'the-perfect-gem' that is 'zomg, so good'
+
+    Then a commit with the message 'Initial commit to the-perfect-gem.' is made
+    And 'README.rdoc' was checked in
+    And 'Rakefile' was checked in
+    And 'LICENSE' was checked in
+    And 'lib/the-perfect-gem.rb' was checked in
+    And '.gitignore' was checked in
+
+    And no files are untracked
+    And no files are changed
+    And no files are added
+    And no files are deleted
+
+  Scenario: bacon
+    Given a working directory
+    And I have configured git sanely
+    When I generate a bacon project named 'the-perfect-gem' that is 'zomg, so good'
+
+    Then 'spec/spec_helper.rb' was checked in
+    And 'spec/the-perfect-gem_spec.rb' was checked in
+
+  Scenario: minitest
+    Given a working directory
+    And I have configured git sanely
+    When I generate a minitest project named 'the-perfect-gem' that is 'zomg, so good'
+
+    Then 'test/helper.rb' was checked in
+    And 'test/test_the-perfect-gem.rb' was checked in
+
+  Scenario: rspec
+    Given a working directory
+    And I have configured git sanely
+    When I generate a rspec project named 'the-perfect-gem' that is 'zomg, so good'
+
+    Then 'spec/spec_helper.rb' was checked in
+    And 'spec/the-perfect-gem_spec.rb' was checked in
+
+  Scenario: shoulda
+    Given a working directory
+    And I have configured git sanely
+    When I generate a shoulda project named 'the-perfect-gem' that is 'zomg, so good'
+
+    Then 'test/helper.rb' was checked in
+    And 'test/test_the-perfect-gem.rb' was checked in
+
+  Scenario: testunit
+    Given a working directory
+    And I have configured git sanely
+    When I generate a testunit project named 'the-perfect-gem' that is 'zomg, so good'
+
+    Then 'test/helper.rb' was checked in
+    And 'test/test_the-perfect-gem.rb' was checked in
+
+  Scenario: micronaut
+    Given a working directory
+    And I have configured git sanely
+    When I generate a micronaut project named 'the-perfect-gem' that is 'zomg, so good'
+
+    Then 'examples/example_helper.rb' was checked in
+    And 'examples/the-perfect-gem_example.rb' was checked in
+
+  Scenario: cucumber
+    Given a working directory
+    And I have configured git sanely
+    And I want cucumber stories
+    When I generate a project named 'the-perfect-gem' that is 'zomg, so good'
+
+    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

data/vendor/ruby/1.8/gems/jeweler-1.4.0/features/generator/license.feature

@@ -0,0 +1,11 @@
+Feature: generated license
+  In order to start a new gem
+  A user should be able to
+  generate a default license
+
+  Scenario: copyright
+    Given a working directory
+    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'

data/vendor/ruby/1.8/gems/jeweler-1.4.0/features/generator/rakefile.feature

@@ -0,0 +1,151 @@
+Feature: generated Rakefile
+  In order to start a new gem
+  A user should be able to
+  generate a Rakefile
+
+  Background:
+    Given a working directory
+    And I have configured git sanely
+
+  Scenario: shared
+    When I generate a project named 'the-perfect-gem' that is 'zomg, so good' and described as 'Descriptive'
+
+    Then 'Rakefile' requires 'rubygems'
+    And 'Rakefile' requires 'rake'
+    And 'Rakefile' requires 'rake/rdoctask'
+    And Rakefile has 'the-perfect-gem' for the Jeweler::Tasks name
+    And Rakefile has 'bar@example.com' for the Jeweler::Tasks email
+    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
+
+  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
+    And Rakefile has 'spec' in the Rcov::RcovTask libs
+    And Rakefile has "spec" as the default task
+
+  Scenario: minitest
+    When I generate a minitest project named 'the-perfect-gem' that is 'zomg, so good'
+
+    Then 'Rakefile' requires 'rcov/rcovtask'
+    And Rakefile has 'test/**/test_*.rb' for the Rake::TestTask pattern
+    And Rakefile has 'test/**/test_*.rb' for the Rcov::RcovTask pattern
+    And Rakefile has 'test' in the Rcov::RcovTask libs
+    And Rakefile has "test" as the default task
+
+  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
+    And Rakefile has "spec" as the default task
+
+  Scenario: shoulda
+    When I generate a shoulda project named 'the-perfect-gem' that is 'zomg, so good'
+
+    Then 'Rakefile' requires 'rcov/rcovtask'
+    And Rakefile has 'test/**/test_*.rb' for the Rake::TestTask pattern
+    And Rakefile has 'test/**/test_*.rb' for the Rcov::RcovTask pattern
+    And Rakefile has 'test' in the Rcov::RcovTask libs
+    And Rakefile has "test" as the default task
+
+  Scenario: micronaut
+    When I generate a micronaut project named 'the-perfect-gem' that is 'zomg, so good'
+
+    Then 'Rakefile' requires 'micronaut/rake_task'
+    And Rakefile has 'examples/**/*_example.rb' for the Micronaut::RakeTask pattern
+    And Rakefile has "examples" as the default task
+
+  Scenario: testunit
+    When I generate a testunit project named 'the-perfect-gem' that is 'zomg, so good'
+
+    Then 'Rakefile' requires 'rcov/rcovtask'
+    Then Rakefile has 'test/**/test_*.rb' for the Rake::TestTask pattern
+    And Rakefile has 'test/**/test_*.rb' for the Rcov::RcovTask pattern
+    And Rakefile has 'test' in the Rcov::RcovTask libs
+    And Rakefile has "test" as the default task
+
+  Scenario: no cucumber
+    Given I do not want cucumber stories
+    When I generate a testunit project named 'the-perfect-gem' that is 'zomg, so good'
+    Then Rakefile does not require 'cucumber/rake/task'
+    And Rakefile does not instantiate a Cucumber::Rake::Task
+
+  Scenario: cucumber
+    Given I want cucumber stories
+    When I generate a testunit project named 'the-perfect-gem' that is 'zomg, so good'
+    Then Rakefile requires 'cucumber/rake/task'
+    And Rakefile instantiates a Cucumber::Rake::Task
+
+  Scenario: no reek
+    Given I do not want reek
+    When I generate a testunit project named 'the-perfect-gem' that is 'zomg, so good'
+    Then Rakefile does not require 'reek/adapters/rake_task'
+    And Rakefile does not instantiate a Reek::RakeTask
+
+  Scenario: reek
+    Given I want reek
+    When I generate a testunit project named 'the-perfect-gem' that is 'zomg, so good'
+    Then Rakefile requires 'reek/adapters/rake_task'
+    And Rakefile instantiates a Reek::RakeTask
+
+  Scenario: no roodi
+    Given I do not want roodi
+    When I generate a testunit project named 'the-perfect-gem' that is 'zomg, so good'
+    Then Rakefile does not require 'roodi'
+    And Rakefile does not require 'roodi_task'
+    And Rakefile does not instantiate a RoodiTask
+
+  Scenario: roodi
+    Given I want roodi
+    When I generate a testunit project named 'the-perfect-gem' that is 'zomg, so good'
+    Then Rakefile requires 'roodi'
+    And Rakefile requires 'roodi_task'
+    And Rakefile instantiates a RoodiTask
+
+  Scenario: no rubyforge
+    Given I do not want rubyforge setup
+    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'
+
+    Then 'Rakefile' does not require 'rake/rdoctask'
+    And 'Rakefile' requires 'yard'
+    And Rakefile instantiates a YARD::Rake::YardocTask
+
+  Scenario: rdoc
+    Given I want to use rdoc instead of yard
+    When I generate a testunit project named 'the-perfect-gem' that is 'zomg, so good'
+
+    Then 'Rakefile' does not require 'yard'
+    And 'Rakefile' requires 'rake/rdoctask'
+    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: 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

data/vendor/ruby/1.8/gems/jeweler-1.4.0/features/generator/readme.feature

@@ -0,0 +1,12 @@
+Feature: generated license
+  In order to start a new gem
+  A user should be able to
+  generate a default license
+
+  Scenario: copyright
+    Given a working directory
+    And I have configured git sanely
+    When I generate a project named 'the-perfect-gem' that is 'zomg, so good'
+
+    Then 'README.rdoc' contains '= the-perfect-gem'
+    And 'README.rdoc' mentions copyright belonging to me in the current year

data/vendor/ruby/1.8/gems/jeweler-1.4.0/features/generator/test.feature

@@ -0,0 +1,48 @@
+Feature: generated test or spec
+  In order to start a new gem
+  A user should be able to
+  generate a test or spec
+
+  Scenario: bacon
+    Given a working directory
+    And I have configured git sanely
+    When I generate a bacon project named 'the-perfect-gem' that is 'zomg, so good'
+    Then 'spec/the-perfect-gem_spec.rb' should describe 'ThePerfectGem'
+
+  Scenario: minitest
+    Given a working directory
+    And I have configured git sanely
+    When I generate a minitest project named 'the-perfect-gem' that is 'zomg, so good'
+    Then 'test/test_the-perfect-gem.rb' should define 'TestThePerfectGem' as a subclass of 'MiniTest::Unit::TestCase'
+
+  Scenario: rspec
+    Given a working directory
+    And I have configured git sanely
+    When I generate a rspec project named 'the-perfect-gem' that is 'zomg, so good'
+    Then 'spec/the-perfect-gem_spec.rb' should describe 'ThePerfectGem'
+
+  Scenario: shoulda
+    Given a working directory
+    And I have configured git sanely
+    And I intend to test with shoulda
+    When I generate a project named 'the-perfect-gem' that is 'zomg, so good'
+    Then 'test/test_the-perfect-gem.rb' should define 'TestThePerfectGem' as a subclass of 'Test::Unit::TestCase'
+
+  Scenario: testunit
+    Given a working directory
+    And I have configured git sanely
+    When I generate a testunit project named 'the-perfect-gem' that is 'zomg, so good'
+    Then 'test/test_the-perfect-gem.rb' should define 'TestThePerfectGem' as a subclass of 'Test::Unit::TestCase'
+
+  Scenario: micronaut
+    Given a working directory
+    And I have configured git sanely
+    When I generate a micronaut project named 'the-perfect-gem' that is 'zomg, so good'
+    Then 'examples/the-perfect-gem_example.rb' should describe 'ThePerfectGem'
+
+  Scenario: riot
+    Given a working directory
+      And I have configured git sanely
+    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'

data/vendor/ruby/1.8/gems/jeweler-1.4.0/features/generator/test_helper.feature

@@ -0,0 +1,56 @@
+Feature: generated test or spec
+  In order to start a new gem
+  A user should be able to
+  generate a test or spec
+
+  Scenario: bacon
+    Given a working directory
+    And I have configured git sanely
+    When I generate a bacon project named 'the-perfect-gem' that is 'zomg, so good'
+    Then 'spec/spec_helper.rb' requires 'bacon'
+    And 'spec/spec_helper.rb' requires 'the-perfect-gem'
+
+  Scenario: minitest
+    Given a working directory
+    And I have configured git sanely
+    When I generate a minitest project named 'the-perfect-gem' that is 'zomg, so good'
+    Then 'test/helper.rb' requires 'minitest/unit'
+    And 'test/helper.rb' requires 'the-perfect-gem'
+    And 'test/helper.rb' should autorun tests
+
+  Scenario: rspec
+    Given a working directory
+    And I have configured git sanely
+    When I generate a rspec project named 'the-perfect-gem' that is 'zomg, so good'
+    Then 'spec/spec_helper.rb' requires 'spec'
+    And 'spec/spec_helper.rb' requires 'the-perfect-gem'
+
+  Scenario: shoulda
+    Given a working directory
+    And I have configured git sanely
+    When I generate a shoulda project named 'the-perfect-gem' that is 'zomg, so good'
+    Then 'test/helper.rb' requires 'test/unit'
+    And 'test/helper.rb' requires 'shoulda'
+    And 'test/helper.rb' requires 'the-perfect-gem'
+
+  Scenario: testunit
+    Given a working directory
+    And I have configured git sanely
+    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'
+
+  Scenario: micronaut
+    Given a working directory
+    And I have configured git sanely
+    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'
+
+  Scenario: riot
+    Given a working directory
+      And I have configured git sanely
+    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'

data/vendor/ruby/1.8/gems/jeweler-1.4.0/features/placeholder.feature

@@ -0,0 +1,5 @@
+Feature: I am a placeholder
+
+    Scenario: I am also a placeholder
+      Given a working directory
+

data/vendor/ruby/1.8/gems/jeweler-1.4.0/features/step_definitions/debug_steps.rb

@@ -0,0 +1,6 @@
+Then /^I debug$/ do
+  require 'ruby-debug'
+  breakpoint
+  0
+end
+

data/vendor/ruby/1.8/gems/jeweler-1.4.0/features/step_definitions/filesystem_steps.rb

@@ -0,0 +1,68 @@
+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
+end
+
+Given /^I use the jeweler command to generate the "([^"]+)" project in the working directory$/ do |name|
+  @name = name
+
+  return_to = Dir.pwd
+  path_to_jeweler = File.expand_path File.join(File.dirname(__FILE__), '..', '..', 'bin', 'jeweler')
+
+  begin
+    FileUtils.cd @working_dir
+    @stdout = `#{path_to_jeweler} #{@name}`
+  ensure
+    FileUtils.cd return_to
+  end
+end
+
+Given /^"([^"]+)" does not exist$/ do |file|
+  assert ! File.exists?(File.join(@working_dir, file))
+end
+
+When /^I run "([^"]+)" in "([^"]+)"$/ do |command, directory|
+  full_path = File.join(@working_dir, directory)
+
+  lib_path = File.expand_path 'lib'
+  command.gsub!(/^rake /, "rake --trace -I#{lib_path} ")
+
+  assert File.directory?(full_path), "#{full_path} is not a directory"
+
+  @stdout = `cd #{full_path} && #{command}`
+  @exited_cleanly = $?.exited?
+end
+
+Then /^the updated version, (.*), is displayed$/ do |version|
+  assert_match "Updated version: #{version}", @stdout
+end
+
+Then /^the current version, (\d+\.\d+\.\d+), is displayed$/ do |version|
+  assert_match "Current version: #{version}", @stdout
+end
+
+Then /^the process should exit cleanly$/ do
+  assert @exited_cleanly, "Process did not exit cleanly: #{@stdout}"
+end
+
+Then /^the process should not exit cleanly$/ do
+  assert !@exited_cleanly, "Process did exit cleanly: #{@stdout}"
+end
+
+Given /^I use the existing project "([^"]+)" as a template$/ do |fixture_project|
+  @name = fixture_project
+  FileUtils.cp_r File.join(fixture_dir, fixture_project), @working_dir
+end
+
+Given /^"VERSION\.yml" contains hash "([^"]+)"$/ do |ruby_string|
+  version_hash = YAML.load(File.read(File.join(@working_dir, @name, 'VERSION.yml')))
+  evaled_hash = eval(ruby_string)
+  assert_equal evaled_hash, version_hash
+end
+
+Given /^"VERSION" contains "([^\"]*)"$/ do |expected|
+  version = File.read(File.join(@working_dir, @name, 'VERSION')).chomp
+  assert_equal expected, version
+end
+