RubyGems - jeweler2 - Versions diffs - 2.0.1 → 2.0.2 - Mend

jeweler2 2.0.1 → 2.0.2

Files changed (117) hide show

data/lib/jeweler/version.rb +1 -1
metadata +30 -145
data/.document +0 -8
data/Gemfile +0 -18
data/Gemfile.lock +0 -47
data/Rakefile +0 -80
data/features/generator/cucumber.feature +0 -103
data/features/generator/directory_layout.feature +0 -86
data/features/generator/dotdocument.feature +0 -13
data/features/generator/env_options.feature +0 -9
data/features/generator/gemfile.feature +0 -71
data/features/generator/git.feature +0 -102
data/features/generator/license.feature +0 -20
data/features/generator/rakefile.feature +0 -158
data/features/generator/readme.feature +0 -12
data/features/generator/test.feature +0 -54
data/features/generator/test_helper.feature +0 -149
data/features/placeholder.feature +0 -5
data/features/step_definitions/debug_steps.rb +0 -6
data/features/step_definitions/filesystem_steps.rb +0 -70
data/features/step_definitions/generator_steps.rb +0 -380
data/features/step_definitions/task_steps.rb +0 -6
data/features/support/env.rb +0 -42
data/features/tasks/build_gem.feature +0 -9
data/features/tasks/version.feature +0 -31
data/features/tasks/version_bumping.feature +0 -49
data/jeweler.gemspec +0 -245
data/jeweler2.gemspec +0 -233
data/lib/jeweler/templates/.document +0 -5
data/lib/jeweler/templates/.gitignore +0 -48
data/lib/jeweler/templates/Gemfile +0 -12
data/lib/jeweler/templates/LICENSE.txt +0 -20
data/lib/jeweler/templates/README.rdoc +0 -19
data/lib/jeweler/templates/Rakefile +0 -9
data/lib/jeweler/templates/bacon/flunking.rb +0 -7
data/lib/jeweler/templates/bacon/helper.rb +0 -9
data/lib/jeweler/templates/bundler_setup.erb +0 -10
data/lib/jeweler/templates/features/default.feature +0 -9
data/lib/jeweler/templates/features/support/env.rb +0 -10
data/lib/jeweler/templates/jeweler_tasks.erb +0 -31
data/lib/jeweler/templates/micronaut/flunking.rb +0 -7
data/lib/jeweler/templates/micronaut/helper.rb +0 -18
data/lib/jeweler/templates/minitest/flunking.rb +0 -7
data/lib/jeweler/templates/minitest/helper.rb +0 -12
data/lib/jeweler/templates/other_tasks.erb +0 -86
data/lib/jeweler/templates/riot/flunking.rb +0 -11
data/lib/jeweler/templates/riot/helper.rb +0 -4
data/lib/jeweler/templates/rspec/.rspec +0 -1
data/lib/jeweler/templates/rspec/flunking.rb +0 -7
data/lib/jeweler/templates/rspec/helper.rb +0 -12
data/lib/jeweler/templates/shindo/flunking.rb +0 -8
data/lib/jeweler/templates/shindo/helper.rb +0 -6
data/lib/jeweler/templates/shoulda/flunking.rb +0 -7
data/lib/jeweler/templates/shoulda/helper.rb +0 -11
data/lib/jeweler/templates/testspec/flunking.rb +0 -7
data/lib/jeweler/templates/testspec/helper.rb +0 -7
data/lib/jeweler/templates/testunit/flunking.rb +0 -7
data/lib/jeweler/templates/testunit/helper.rb +0 -10
data/test/fixtures/bar/VERSION.yml +0 -4
data/test/fixtures/bar/bin/foo_the_ultimate_bin +0 -1
data/test/fixtures/bar/hey_include_me_in_gemspec +0 -0
data/test/fixtures/bar/lib/foo_the_ultimate_lib.rb +0 -1
data/test/fixtures/existing-project-with-version-constant/.document +0 -5
data/test/fixtures/existing-project-with-version-constant/.gitignore +0 -5
data/test/fixtures/existing-project-with-version-constant/LICENSE.txt +0 -20
data/test/fixtures/existing-project-with-version-constant/README.rdoc +0 -7
data/test/fixtures/existing-project-with-version-constant/Rakefile +0 -85
data/test/fixtures/existing-project-with-version-constant/existing-project-with-version.gemspec +0 -29
data/test/fixtures/existing-project-with-version-constant/lib/existing_project_with_version.rb +0 -0
data/test/fixtures/existing-project-with-version-constant/test/existing_project_with_version_test.rb +0 -7
data/test/fixtures/existing-project-with-version-constant/test/test_helper.rb +0 -10
data/test/fixtures/existing-project-with-version-plaintext/.document +0 -5
data/test/fixtures/existing-project-with-version-plaintext/.gitignore +0 -5
data/test/fixtures/existing-project-with-version-plaintext/LICENSE.txt +0 -20
data/test/fixtures/existing-project-with-version-plaintext/README.rdoc +0 -7
data/test/fixtures/existing-project-with-version-plaintext/Rakefile +0 -84
data/test/fixtures/existing-project-with-version-plaintext/VERSION +0 -1
data/test/fixtures/existing-project-with-version-plaintext/existing-project-with-version.gemspec +0 -29
data/test/fixtures/existing-project-with-version-plaintext/lib/existing_project_with_version.rb +0 -0
data/test/fixtures/existing-project-with-version-plaintext/test/existing_project_with_version_test.rb +0 -7
data/test/fixtures/existing-project-with-version-plaintext/test/test_helper.rb +0 -10
data/test/fixtures/existing-project-with-version-yaml/.document +0 -5
data/test/fixtures/existing-project-with-version-yaml/.gitignore +0 -5
data/test/fixtures/existing-project-with-version-yaml/LICENSE.txt +0 -20
data/test/fixtures/existing-project-with-version-yaml/README.rdoc +0 -7
data/test/fixtures/existing-project-with-version-yaml/Rakefile +0 -84
data/test/fixtures/existing-project-with-version-yaml/VERSION.yml +0 -4
data/test/fixtures/existing-project-with-version-yaml/bin/foo_the_ultimate_bin +0 -0
data/test/fixtures/existing-project-with-version-yaml/existing-project-with-version.gemspec +0 -29
data/test/fixtures/existing-project-with-version-yaml/lib/existing_project_with_version.rb +0 -0
data/test/fixtures/existing-project-with-version-yaml/test/existing_project_with_version_test.rb +0 -7
data/test/fixtures/existing-project-with-version-yaml/test/test_helper.rb +0 -10
data/test/geminstaller.yml +0 -12
data/test/jeweler/commands/test_build_gem.rb +0 -103
data/test/jeweler/commands/test_install_gem.rb +0 -35
data/test/jeweler/commands/test_release_to_gemcutter.rb +0 -39
data/test/jeweler/commands/test_release_to_git.rb +0 -198
data/test/jeweler/commands/test_release_to_github.rb +0 -390
data/test/jeweler/commands/test_validate_gemspec.rb +0 -27
data/test/jeweler/commands/test_write_gemspec.rb +0 -101
data/test/jeweler/commands/version/test_base.rb +0 -32
data/test/jeweler/commands/version/test_bump_major.rb +0 -22
data/test/jeweler/commands/version/test_bump_minor.rb +0 -19
data/test/jeweler/commands/version/test_bump_patch.rb +0 -20
data/test/jeweler/commands/version/test_write.rb +0 -22
data/test/jeweler/generator/test_application.rb +0 -120
data/test/jeweler/generator/test_options.rb +0 -225
data/test/jeweler/test_gemspec_helper.rb +0 -44
data/test/jeweler/test_generator.rb +0 -141
data/test/jeweler/test_generator_initialization.rb +0 -164
data/test/jeweler/test_generator_mixins.rb +0 -23
data/test/jeweler/test_specification.rb +0 -237
data/test/jeweler/test_tasks.rb +0 -50
data/test/jeweler/test_version_helper.rb +0 -214
data/test/shoulda_macros/jeweler_macros.rb +0 -35
data/test/test_helper.rb +0 -178
data/test/test_jeweler.rb +0 -175

data/features/generator/cucumber.feature DELETED

@@ -1,103 +0,0 @@
-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 'bundler'
-    And 'features/support/env.rb' sets up bundler using the default and development groups
-    And 'features/support/env.rb' requires 'the-perfect-gem'
-  Scenario: bundler
-    Given a working directory
-    And I want bundler
-    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'
-    And 'features/support/env.rb' requires 'bundler'
-    And 'features/support/env.rb' sets up bundler using the default and development groups
-  Scenario: no bundler
-    Given a working directory
-    And I have configured git sanely
-    And I do not want bundler
-    And I want cucumber stories
-    When I generate a project named 'the-perfect-gem' that is 'zomg, so good'
-    And 'features/support/env.rb' does not require 'bundler'
-    And 'features/support/env.rb' does not setup bundler
-  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 'rspec/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 DELETED

@@ -1,86 +0,0 @@
-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
-  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 a directory named 'the-perfect-gem/tests' is created
-    And a file named 'the-perfect-gem/tests/tests_helper.rb' is created
-    And a file named 'the-perfect-gem/tests/the-perfect-gem_tests.rb' is created

data/features/generator/dotdocument.feature DELETED

@@ -1,13 +0,0 @@
-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 'lib/**/*.rb'
-    And '.document' contains 'bin/*'
-    And '.document' contains 'features/**/*.feature'
-    And '.document' contains 'LICENSE.txt'

data/features/generator/env_options.feature DELETED

@@ -1,9 +0,0 @@
-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/gemfile.feature DELETED

@@ -1,71 +0,0 @@
-Feature: generated Gemfiel
-  In order to start a new gem
-  A user should be able to
-  generate a Gemfile
-  Background:
-    Given a working directory
-    And I have configured git sanely
-  Scenario: disabled
-    Given I do not want bundler
-    When I generate a project named 'the-perfect-gem' that is 'zomg, so good'
-    Then a file named 'the-perfect-gemGemfile' is not created
-  Scenario: enabled
-    Given I want bundler
-    When I generate a project named 'the-perfect-gem' that is 'zomg, so good'
-    Then a file named 'the-perfect-gem/Gemfile' is created
-  Scenario: default
-    When I generate a project named 'the-perfect-gem' that is 'zomg, so good'
-    Then a file named 'the-perfect-gem/Gemfile' is created
-    And 'Gemfile' uses the gemcutter source
-    And 'Gemfile' has a development dependency on 'bundler'
-    And 'Gemfile' has a development dependency on the current version of jeweler
-    And 'Gemfile' has a development dependency on 'rcov'
-  Scenario: bacon
-    When I generate a bacon project named 'the-perfect-gem' that is 'zomg, so good'
-    Then 'Gemfile' has a development dependency on 'bacon'
-  Scenario: minitest
-    When I generate a minitest project named 'the-perfect-gem' that is 'zomg, so good'
-    Then 'Gemfile' has a development dependency on 'minitest'
-  Scenario: rspec
-    When I generate a rspec project named 'the-perfect-gem' that is 'zomg, so good'
-    Then 'Gemfile' has a development dependency on 'rspec'
-  Scenario: shoulda
-    When I generate a shoulda project named 'the-perfect-gem' that is 'zomg, so good'
-    Then 'Gemfile' has a development dependency on 'shoulda'
-  Scenario: micronaut
-    When I generate a micronaut project named 'the-perfect-gem' that is 'zomg, so good'
-    Then 'Gemfile' has a development dependency on 'micronaut'
-  Scenario: cucumber
-    Given I want cucumber stories
-    When I generate a testunit project named 'the-perfect-gem' that is 'zomg, so good'
-    Then 'Gemfile' has a development dependency on 'cucumber'
-  Scenario: reek
-    Given I want reek
-    When I generate a testunit project named 'the-perfect-gem' that is 'zomg, so good'
-    Then 'Gemfile' has a development dependency on 'reek'
-  Scenario: roodi
-    Given I want roodi
-    When I generate a testunit project named 'the-perfect-gem' that is 'zomg, so good'
-    Then 'Gemfile' has a development dependency on 'roodi'
-  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 'Gemfile' has a development dependency on 'yard'
-  Scenario: shindo
-    When I generate a shindo project named 'the-perfect-gem' that is 'zomg, so good'
-    Then 'Gemfile' has a development dependency on 'shindo'

data/features/generator/git.feature DELETED

@@ -1,102 +0,0 @@
-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.txt' 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
-  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 DELETED

@@ -1,20 +0,0 @@
-Feature: generated license
-  In order to start a new gem
-  A user should be able to
-  generate a default license
-  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.txt 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.txt has a copyright in the year 2005

data/features/generator/rakefile.feature DELETED

@@ -1,158 +0,0 @@
-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 '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
-    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
-    And Rakefile has 'MIT' for the Jeweler::Tasks license
-    And Rakefile instantiates a Jeweler::RubygemsDotOrgTasks
-    And Rakefile has a magic comment for UTF-8
-  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
-  @rspec
-  Scenario: rspec
-    When I generate a rspec project named 'the-perfect-gem' that is 'zomg, so good'
-    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
-    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 '--exclude "gems/*"' in the Rcov::RcovTask rcov_opts
-    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/rake/task'
-    And Rakefile does not instantiate a Reek::Rake::Task
-  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/rake/task'
-    And Rakefile instantiates a Reek::Rake::Task
-  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: 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: 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: 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
-    And Rakefile does not add 'jeweler' as a development dependency to Jeweler::Tasks
-  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
-    And Rakefile adds 'jeweler' as a development dependency to Jeweler::Tasks