technicalpickles-jeweler 0.11.0 → 1.0.0

data/.gitignore

@@ -0,0 +1,7 @@
+coverage
+pkg
+rdoc
+tags
+test/tmp
+test/version_tmp
+tmp

data/ChangeLog.markdown

@@ -1,3 +1,11 @@
+# jeweler 0.11.1
+
+ * Lots of internal refactorings to how project generation happens
+ * Fixed missing dependency on rubyforge
+ * Depend on a recent version of schacon-git which works on ruby 1.9
+ * Updated cucumber support for 0.3.x
+ * Tested on Ruby 1.9
+
 # jeweler 0.11.0 2009-04-05
 
  * generator will respect JEWELER_OPTS, as a way to provide default options

data/README.markdown

@@ -5,12 +5,16 @@ Jeweler provides two things:
  * Rake tasks for managing gems and versioning of a <a href="http://github.com">GitHub</a> project
  * A generator for creating kickstarting a new project
 
+## Quick Links
+
+ * [Wiki](http://wiki.github.com/technicalpickles/jeweler)
+ * [Bugs](http://github.com/technicalpickles/jeweler/issues)
+ * [Donate](http://pledgie.org/campaigns/2604)
+
 ## Installing
 
-    # Run the following if you haven't done so before:
-    gem sources -a http://gems.github.com
     # Install the gem:
-    sudo gem install technicalpickles-jeweler
+    sudo gem install jeweler
     
 ## Using in an existing project
 
@@ -30,7 +34,7 @@ It's easy to get up and running. Update your Rakefile to instantiate a `Jeweler:
       puts "Jeweler not available. Install it with: sudo gem install technicalpickles-jeweler -s http://gems.github.com"
     end
 
-The yield object here, `gemspec`, is a `Gem::Specification` object. See the [GemSpec reference](http://www.rubygems.org/read/chapter/20) for the full details on `Gem::Specification`.
+The yield object here, `gemspec`, is a `Gem::Specification` object. See the [Customizing your project's gem specification](http://wiki.github.com/technicalpickles/jeweler/customizing-your-projects-gem-specification) for more details about how you can customize your gemspec.
 
 ## Using to start a new project
 
@@ -119,7 +123,7 @@ With this in place, you now update your Jeweler::Tasks to setup `rubyforge_proje
         s.rubyforge_project = 'the-perfect-gem' # This line would be new
       end
     rescue LoadError
-      puts "Jeweler not available. Install it with: sudo gem install technicalpickles-jeweler -s http://gems.github.com"
+      puts "Jeweler not available. Install it with: sudo gem install jeweler"
     end
 
     # These are new tasks
@@ -164,7 +168,3 @@ With all that setup out of the way, you can now release to RubyForge with impuni
  * Have a delicious scotch
  * Install [gemstalker](http://github.com/technicalpickles/gemstalker), and use it to know when gem is built. It typically builds in a few minutes, but won't be installable for another 15 minutes.
 
-## Links
-
- * [Bugs](http://technicalpickles.lighthouseapp.com/projects/23560-jeweler/overview)
- * [Donate](http://pledgie.org/campaigns/2604)

data/ROADMAP

@@ -0,0 +1,12 @@
+= 1.0
+
+ * Improve documentation on wiki/readme
+
+= Unscheduled, or waiting for contributions
+
+ * Add command to output the Jeweler::Tasks to help with upgrading/migrating
+ * Support github user/token on generator command line
+ * Support C extensions
+ * Support JRuby gems
+ * Support thor
+ * Dealing with version bumps in other remotes

data/Rakefile

@@ -2,6 +2,9 @@ require 'rake'
 
 $LOAD_PATH.unshift('lib')
 
+gem 'git'
+require 'git'
+
 begin
   require 'jeweler'
   Jeweler::Tasks.new do |gem|
@@ -12,19 +15,21 @@ begin
     gem.description = "Simple and opinionated helper for creating Rubygem projects on GitHub"
     gem.authors = ["Josh Nichols"]
     gem.files.include %w(lib/jeweler/templates/.document lib/jeweler/templates/.gitignore)
-    gem.add_dependency "peterwald-git"
+    gem.add_dependency "git", ">= 1.1.1"
+    gem.add_dependency "rubyforge"
     gem.rubyforge_project = "pickles"
   end
 rescue LoadError
-  puts "Jeweler, or one of its dependencies, is not available. Install it with: sudo gem install technicalpickles-jeweler -s http://gems.github.com"
+  puts "Jeweler, or one of its dependencies, is not available. Install it with: sudo gem install jeweler"
 end
 
 require 'rake/testtask'
 Rake::TestTask.new(:test) do |test|
-  test.pattern = 'test/**/test_*.rb'
+  test.test_files = FileList.new('test/**/test_*.rb') do |list|
+    list.exclude 'test/test_helper.rb'
+  end
   test.libs << 'test'
   test.verbose = true
-  #test.ruby_opts << '-rtest_helper'
 end
 
 require 'rake/rdoctask'
@@ -49,11 +54,23 @@ end
 
 begin
   require 'cucumber/rake/task'
-  Cucumber::Rake::Task.new(:features)
+  Cucumber::Rake::Task.new(:features) do |features|
+    features.cucumber_opts = "features --format progress"
+  end
+  namespace :features do
+    Cucumber::Rake::Task.new(:pretty) do |features|
+      features.cucumber_opts = "features --format progress"
+    end
+  end
 rescue LoadError
   task :features do
     abort "Cucumber is not available. In order to run features, you must: sudo gem install cucumber"
   end
+  namespace :features do
+    task :pretty do
+      abort "Cucumber is not available. In order to run features, you must: sudo gem install cucumber"
+    end
+  end
 end
 
 begin

data/VERSION.yml

@@ -1,4 +1,4 @@
 --- 
-:major: 0
-:minor: 11
+:minor: 0
 :patch: 0
+:major: 1

data/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 'mini/test'
+    And cucumber world extends "Mini::Test::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/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/test_helper.rb' is created
+    And a file named 'the-perfect-gem/test/the-perfect-gem_test.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/test_helper.rb' is created
+    And a file named 'the-perfect-gem/test/the-perfect-gem_test.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/test_helper.rb' is created
+    And a file named 'the-perfect-gem/test/the-perfect-gem_test.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/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/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/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/test_helper.rb' was checked in
+    And 'test/the-perfect-gem_test.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/test_helper.rb' was checked in
+    And 'test/the-perfect-gem_test.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/test_helper.rb' was checked in
+    And 'test/the-perfect-gem_test.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/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/features/generator/rakefile.feature

@@ -0,0 +1,110 @@
+Feature: generated Rakefile
+  In order to start a new gem
+  A user should be able to
+  generate a Rakefile
+
+  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 '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 'http://github.com/technicalpickles/the-perfect-gem' for the Jeweler::Tasks homepage
+
+  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 '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
+    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 '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
+    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 '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
+    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 '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
+    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 '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
+    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 '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 a working directory
+    And I have configured git sanely
+    And 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 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 Rakefile requires 'cucumber/rake/task' 
+    And Rakefile instantiates a Cucumber::Rake::Task
+
+  Scenario: no rubyforge
+    Given a working directory
+    And I have configured git sanely
+    And 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 a working directory
+    And I have configured git sanely
+    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

data/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/features/generator/test.feature

@@ -0,0 +1,41 @@
+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/the-perfect-gem_test.rb' should define 'ThePerfectGemTest' as a subclass of 'Mini::Test::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/the-perfect-gem_test.rb' should define 'ThePerfectGemTest' 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/the-perfect-gem_test.rb' should define 'ThePerfectGemTest' 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'

data/features/generator/test_helper.feature

@@ -0,0 +1,49 @@
+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/test_helper.rb' requires 'mini/test'
+    And 'test/test_helper.rb' requires 'the-perfect-gem'
+    And 'test/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/test_helper.rb' requires 'test/unit'
+    And 'test/test_helper.rb' requires 'shoulda'
+    And 'test/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/test_helper.rb' requires 'test/unit'
+    And 'test/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'

data/features/placeholder.feature

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