newgem 1.3.0 → 1.4.0

data/History.txt

@@ -1,3 +1,12 @@
+== 1.4.0 2009-05-02
+
+* install_shoulda - use "newgem -T shoulda" to use shoulda for testing instead of test_unit or rspec
+* common_steps.rb - When steps all started with 'I ...'
+* common.rb - using module instead of creating methods against global namespace; no more kittens killed [thx Ben Mabey]
+* all +require 'rubygems'+ are conditional unless ENV['NO_RUBYGEMS'] [thx David Chelimsky + Ryan Tomayko]
+* module_name supports hyphens throughout all generators (they are treated as underscores for camelize method)
+* common_steps.rb - using "(.*)" for placeholders which is now cucumber defacto standard
+
 == 1.3.0 2009-03-17
 
 * install_cucumber: using layout like Rails' cucumber generator: features/support/env.rb + features/step_definitions/common_steps.rb

data/Manifest.txt

@@ -34,7 +34,6 @@ cucumber_generators/feature/templates/feature.erb
 cucumber_generators/feature/templates/steps.erb
 features/development.feature
 features/executable_generator.feature
-features/expected_outputs/newgem.out
 features/extconf.feature
 features/install_cucumber.feature
 features/install_website.feature
@@ -43,7 +42,10 @@ features/rubygem_tasks.feature
 features/step_definitions/cli_steps.rb
 features/step_definitions/common_steps.rb
 features/step_definitions/rubygems_steps.rb
+features/support/cli.rb
+features/support/common.rb
 features/support/env.rb
+features/support/matchers.rb
 lib/hoe-patched.rb
 lib/newgem.rb
 lib/newgem/quick_template.rb
@@ -91,6 +93,7 @@ rubygems_generators/install_cucumber/USAGE
 rubygems_generators/install_cucumber/install_cucumber_generator.rb
 rubygems_generators/install_cucumber/templates/features/development.feature
 rubygems_generators/install_cucumber/templates/features/step_definitions/common_steps.rb
+rubygems_generators/install_cucumber/templates/features/support/common.rb
 rubygems_generators/install_cucumber/templates/features/support/env.rb.erb
 rubygems_generators/install_jruby/USAGE
 rubygems_generators/install_jruby/install_jruby_generator.rb
@@ -101,6 +104,11 @@ rubygems_generators/install_rspec/templates/spec.rb
 rubygems_generators/install_rspec/templates/spec/spec.opts
 rubygems_generators/install_rspec/templates/spec/spec_helper.rb
 rubygems_generators/install_rspec/templates/tasks/rspec.rake
+rubygems_generators/install_shoulda/USAGE
+rubygems_generators/install_shoulda/install_shoulda_generator.rb
+rubygems_generators/install_shoulda/templates/tasks/shoulda.rake
+rubygems_generators/install_shoulda/templates/test/test.rb
+rubygems_generators/install_shoulda/templates/test/test_helper.rb
 rubygems_generators/install_test_unit/USAGE
 rubygems_generators/install_test_unit/install_test_unit_generator.rb
 rubygems_generators/install_test_unit/templates/test/test.rb

data/Rakefile

@@ -1,4 +1,5 @@
-%w[rubygems rake rake/clean fileutils rubigen].each { |f| require f }
+require 'rubygems' unless ENV['NO_RUBYGEMS']
+%w[rake rake/clean fileutils rubigen].each { |f| require f }
 require File.dirname(__FILE__) + '/lib/newgem'
 
 # Generate all the Rake tasks

data/TODO.markdown

@@ -1,5 +1,11 @@
-## install_cucumber
+## post_rubyflow
 
-* don't generate tasks/cucumber.rake since its already loaded from newgem
+Code blocks:
+* use <code>
+* indent spaces must be &nbsp;
 
-## Rakefile
+Need title + method description
+
+Probably need to move away from current History.txt paragraph parsing
+
+Store rubyflow login details in .hoerc or .rubyforge?

data/app_generators/newgem/newgem_generator.rb

@@ -17,7 +17,7 @@ class NewgemGenerator < RubiGen::Base
 
 
   attr_reader :gem_name, :module_name, :project_name
-  attr_reader :version, :version_str, :author, :email
+  attr_reader :version, :version_str, :author, :email, :project_url
 
   # extensions/option
   attr_reader :test_framework
@@ -33,6 +33,8 @@ class NewgemGenerator < RubiGen::Base
     @gem_name = base_name
     @module_name  = gem_name.gsub('-','_').camelize
     @project_name = @gem_name
+    @github_username = 'FIXME'
+    @project_url  = 'http://github.com/#{github_username}/#{project_name}'
     extract_options
   end
 
@@ -60,6 +62,8 @@ class NewgemGenerator < RubiGen::Base
         m.dependency "install_test_unit", [gem_name], :destination => destination_root, :collision => :force
       when "rspec"
         m.dependency "install_rspec", [gem_name], :destination => destination_root, :collision => :force
+      when "shoulda"
+        m.dependency "install_shoulda", [gem_name], :destination => destination_root, :collision => :force
       end
 
       # Website

data/app_generators/newgem/templates/README.rdoc

@@ -1,6 +1,6 @@
 = <%= gem_name %>
 
-* FIX (url)
+* <%= project_url %>
 
 == DESCRIPTION:
 

data/app_generators/newgem/templates/Rakefile

@@ -1,4 +1,5 @@
-%w[rubygems rake rake/clean fileutils newgem rubigen].each { |f| require f }
+require 'rubygems' unless ENV['NO_RUBYGEMS']
+%w[rake rake/clean fileutils newgem rubigen].each { |f| require f }
 require File.dirname(__FILE__) + '/lib/<%= gem_name %>'
 
 # Generate all the Rake tasks

data/app_generators/newgem_simple/templates/Rakefile

@@ -1,4 +1,4 @@
-require 'rubygems'
+require 'rubygems' unless ENV['NO_RUBYGEMS']
 require 'rake/gempackagetask'
 require 'rubygems/specification'
 require 'date'

data/bin/newgem

@@ -1,6 +1,6 @@
 #!/usr/bin/env ruby
 
-require 'rubygems'
+require 'rubygems' unless ENV['NO_RUBYGEMS']
 require 'rubigen'
 
 if %w(-v --version).include? ARGV.first

data/features/development.feature

@@ -6,8 +6,8 @@ Feature: Development processes of newgem itself (rake tasks)
     
   Scenario: Generate RubyGem
     Given this project is active project folder
-    And 'pkg' folder is deleted
-    When task 'rake gem' is invoked
-    Then folder 'pkg' is created
-    And file with name matching 'pkg/*.gem' is created else you should run "rake manifest" to fix this
-    And gem spec key 'rdoc_options' contains /--mainREADME.rdoc/
+    And "pkg" folder is deleted
+    When I invoke task "rake gem"
+    Then folder "pkg" is created
+    And file with name matching "pkg/*.gem" is created else you should run "rake manifest" to fix this
+    And gem spec key "rdoc_options" contains /--mainREADME.rdoc/

data/features/executable_generator.feature

@@ -5,42 +5,59 @@ Feature: Generate an executable/CLI scaffold
   So that I know the structure for constructing CLIs and can create them quickly
 
   Scenario: Run executable generator with name of executable
-    Given an existing newgem scaffold [called 'my_project']
-    When 'executable' generator is invoked with arguments 'my_app'
-    Then folder 'bin/my_app' is created
-    And file 'bin/my_app' is created
-    And file 'lib/my_app/cli.rb' is created
-    And file 'test/test_my_app_cli.rb' is created
+    Given an existing newgem scaffold [called "my_project"]
+    When I invoke "executable" generator with arguments "my_app"
+    Then folder "bin/my_app" is created
+    And file "bin/my_app" is created
+    And file "lib/my_app/cli.rb" is created
+    And file "test/test_my_app_cli.rb" is created
+    When I run unit tests for test file "test/test_my_app_cli.rb"
+    Then I should see all 1 tests pass
 
   Scenario: Run executable generator with name of executable on rspec project
-    Given an existing newgem scaffold using options '-T rspec' [called 'my_project']
-    When 'executable' generator is invoked with arguments 'my_app'
-    Then folder 'bin/my_app' is created
-    And file 'bin/my_app' is created
-    And file 'lib/my_app/cli.rb' is created
-    And file 'spec/my_app_cli_spec.rb' is created
+    Given an existing newgem scaffold using options "-T rspec" [called "my_project"]
+    When I invoke "executable" generator with arguments "my_app"
+    Then folder "bin/my_app" is created
+    And file "bin/my_app" is created
+    And file "lib/my_app/cli.rb" is created
+    And file "spec/my_app_cli_spec.rb" is created
+    When I enable rspec autorun
+    And I run unit tests for test file "spec/my_app_cli_spec.rb"
+    Then I should see all 1 examples pass
+  
+  Scenario: Run executable generator with name of executable on shoulda project
+    Given an existing newgem scaffold using options "-T shoulda" [called "my_project"]
+    When I invoke "executable" generator with arguments "my_app"
+    Then folder "bin/my_app" is created
+    And file "bin/my_app" is created
+    And file "lib/my_app/cli.rb" is created
+    And file "test/test_my_app_cli.rb" is created
   
   Scenario: Run CLI app from executable generator to show help
-    Given an existing newgem scaffold [called 'my_project']
-    Given 'executable' generator is invoked with arguments 'my_app'
-    When run project executable 'bin/my_app' with arguments '-h'
-    Then help options '-h' and '--help' are displayed
-    Then help options '-p' and '--path' are displayed
+    Given an existing newgem scaffold [called "my_project"]
+    Given I invoke "executable" generator with arguments "my_app"
+    When I run project executable "bin/my_app" with arguments "-h"
+    Then help options "-h" and "--help" are displayed
+    Then help options "-p" and "--path" are displayed
 
   Scenario: Run CLI app from executable generator should not fail
-    Given an existing newgem scaffold [called 'my_project']
-    Given 'executable' generator is invoked with arguments 'my_app'
-    When run project executable 'bin/my_app' with arguments ''
-    Then output does match /lib\/my_app\/cli.rb/
+    Given an existing newgem scaffold [called "my_project"]
+    And I invoke "executable" generator with arguments "my_app"
+    When I run project executable "bin/my_app" with arguments ""
+    Then I should see
+      """
+      lib/my_app/cli.rb
+      """
   
   Scenario: Run unit tests after executable generator should all pass for test/unit
-    Given an existing newgem scaffold [called 'my_project']
-    And 'executable' generator is invoked with arguments 'my_app'
-    When run unit tests for test file 'test/test_my_app_cli.rb'
-    Then all 1 tests pass
+    Given an existing newgem scaffold [called "my_project"]
+    And I invoke "executable" generator with arguments "my_app"
+    When I run unit tests for test file "test/test_my_app_cli.rb"
+    Then I should see all 1 tests pass
 
   Scenario: Run examples after executable generator should all pass for rspec
-    Given an existing newgem scaffold using options '-T rspec' [called 'my_project']
-    And 'executable' generator is invoked with arguments 'my_app'
-    When run unit tests for test file 'spec/my_app_cli_spec.rb'
-    Then all 1 examples pass
+    Given an existing newgem scaffold using options "-T rspec" [called "my_project"]
+    And I invoke "executable" generator with arguments "my_app"
+    When I enable rspec autorun
+    And I run unit tests for test file "spec/my_app_cli_spec.rb"
+    Then I should see all 1 examples pass

data/features/extconf.feature

@@ -4,35 +4,36 @@ Feature: Write and test C-extensions
   I want to generate a scaffold with test/spec support for writing Ruby C-extensions
 
   Scenario: Run extconf generator with name of extension
-    Given an existing newgem scaffold [called 'my_project']
-    When 'extconf' generator is invoked with arguments 'my_ext'
-    Then folder 'ext/my_ext' is created
-    And file 'ext/my_ext/extconf.rb' is created
-    And file 'ext/my_ext/my_ext.c' is created
-    And file 'test/test_my_ext_extn.rb' is created
-    And file '.autotest' is created
-    And contents of file '.autotest' does match /test\/test_.*_extn\.rb/
+    Given an existing newgem scaffold [called "my_project"]
+    When I invoke "extconf" generator with arguments "my_ext"
+    Then folder "ext/my_ext" is created
+    And file "ext/my_ext/extconf.rb" is created
+    And file "ext/my_ext/my_ext.c" is created
+    And file "test/test_my_ext_extn.rb" is created
+    And file ".autotest" is created
+    And file ".autotest" contents does match /test\/test_.*_extn\.rb/
 
   Scenario: Run extconf generator with name of extension on rspec project
-  Given an existing newgem scaffold using options '-T rspec' [called 'my_project']
-    When 'extconf' generator is invoked with arguments 'my_ext'
-    Then folder 'ext/my_ext' is created
-    And file 'ext/my_ext/extconf.rb' is created
-    And file 'ext/my_ext/my_ext.c' is created
-    And file 'spec/my_ext_extn_spec.rb' is created
-    And file '.autotest' is created
-    And contents of file '.autotest' does match /spec\/.*_extn_spec\.rb/
+  Given an existing newgem scaffold using options "-T rspec" [called "my_project"]
+    When I invoke "extconf" generator with arguments "my_ext"
+    Then folder "ext/my_ext" is created
+    And file "ext/my_ext/extconf.rb" is created
+    And file "ext/my_ext/my_ext.c" is created
+    And file "spec/my_ext_extn_spec.rb" is created
+    And file ".autotest" is created
+    And file ".autotest" contents does match /spec\/.*_extn_spec\.rb/
 
   Scenario: Run unit tests after executable generator should all pass for test/unit
-    Given an existing newgem scaffold [called 'my_project']
-    And 'extconf' generator is invoked with arguments 'my_ext'
-    When task 'rake compile' is invoked
-    And run unit tests for test file 'test/test_my_ext_extn.rb'
-    Then all 1 tests pass
+    Given an existing newgem scaffold [called "my_project"]
+    And I invoke "extconf" generator with arguments "my_ext"
+    When I invoke task "rake compile"
+    And I run unit tests for test file "test/test_my_ext_extn.rb"
+    Then I should see all 1 tests pass
 
   Scenario: Run examples after executable generator should all pass for rspec
-    Given an existing newgem scaffold using options '-T rspec' [called 'my_project']
-    And 'extconf' generator is invoked with arguments 'my_ext'
-    When task 'rake compile' is invoked
-    And run unit tests for test file 'spec/my_ext_extn_spec.rb'
-    Then all 1 examples pass
+    Given an existing newgem scaffold using options "-T rspec" [called "my_project"]
+    And I invoke "extconf" generator with arguments "my_ext"
+    When I invoke task "rake compile"
+    And I enable rspec autorun
+    And I run unit tests for test file "spec/my_ext_extn_spec.rb"
+    Then I should see all 1 examples pass

data/features/install_cucumber.feature

@@ -1,29 +1,39 @@
 Feature: RubyGems have features to be described and tested
 
   As a RubyGem developer
-  I want to describe the project's features using Cucumber
+  I want to describe the project"s features using Cucumber
   So that I can describe each feature of the project in readable text
   
   Scenario: Install Cucumber into a RubyGem
-    Given an existing newgem scaffold [called 'my_project']
-    When 'install_cucumber' generator is invoked with arguments ''
-    Then folder 'features/step_definitions' is created
-    Then folder 'features/support' is created
-    And file 'features/development.feature' is created
-    And file 'features/support/env.rb' is created
-    And file 'features/step_definitions/common_steps.rb' is created
-    And file 'tasks/cucumber.rake' is not created as it is loaded via newgem itself
+    Given default env variables setup for name and email
+    And an existing newgem scaffold [called "my_project"]
+    When I invoke "install_cucumber" generator with arguments ""
+    Then folder "features/step_definitions" is created
+    Then folder "features/support" is created
+    And file "features/development.feature" is created
+    And file "features/support/env.rb" is created
+    And file "features/support/common.rb" is created
+    And file "features/support/matchers.rb" is created
+    And file "features/step_definitions/common_steps.rb" is created
+    And file "tasks/cucumber.rake" is not created as it is loaded via newgem itself
 
   Scenario: NewGem and generated gems should share some common files
-    Given an existing newgem scaffold [called 'my_project']
-    When 'install_cucumber' generator is invoked with arguments ''
-    Then gem file 'features/step_definitions/common_steps.rb' and generated file 'features/step_definitions/common_steps.rb' should be the same
-    Then gem file 'features/development.feature' and generated file 'features/development.feature' should be the same
+    Given default env variables setup for name and email
+    And an existing newgem scaffold [called "my_project"]
+    When I invoke "install_cucumber" generator with arguments ""
+    Then gem file "features/step_definitions/common_steps.rb" and generated file "features/step_definitions/common_steps.rb" should be the same
+    Then gem file "features/support/common.rb" and generated file "features/support/common.rb" should be the same
+    Then gem file "features/support/matchers.rb" and generated file "features/support/matchers.rb" should be the same
+    Then gem file "features/development.feature" and generated file "features/development.feature" should be the same
 
-  Scenario: Installed Cucumber includes a 'rake features' task
-    Given an existing newgem scaffold [called 'my_project']
-    And 'install_cucumber' generator is invoked with arguments ''
-    When task 'rake features' is invoked
-    Then task 'rake features' is executed successfully
-    And output does match /\.{6}/
+  Scenario: Installed Cucumber includes a "rake features" task
+    Given an existing newgem scaffold [called "my_project"]
+    And I invoke "install_cucumber" generator with arguments ""
+    And I invoke task "rake manifest"
+    When I invoke task "rake features"
+    Then task "rake features" is executed successfully
+    And I should see
+      """
+      ......
+      """
 

data/features/install_website.feature

@@ -5,10 +5,10 @@ Feature: RubyGems can have a website to promote and teach
   So that I can spend time on the tests and code, and not excessive time on maintenance processes
 
   Scenario: Deploy project website via local rsync
-    Given an existing newgem scaffold [called 'my_project']
+    Given an existing newgem scaffold [called "my_project"]
     And project website configuration for safe folder on local machine
-    When 'install_website' generator is invoked with arguments ''
-    And task 'rake website' is invoked
-    Then file 'website/index.html' is created
-    Then remote file 'index.html' is created after local rsync
-    Then remote folder 'rdoc' is created after local rsync
+    When I invoke "install_website" generator with arguments ""
+    And I invoke task "rake website"
+    Then file "website/index.html" is created
+    Then remote file "index.html" is created after local rsync
+    Then remote folder "rdoc" is created after local rsync

data/features/newgem_cli.feature

@@ -1,4 +1,4 @@
-Feature: Can run 'newgem' to create RubyGem scaffolds
+Feature: Can run "newgem" to create RubyGem scaffolds
 
   As a developer of RubyGems
   I want to create RubyGem scaffolds
@@ -6,80 +6,124 @@ Feature: Can run 'newgem' to create RubyGem scaffolds
 
   Scenario: Run newgem without any arguments
     Given a safe folder
-    Given env variable $RUBYFORGE_USERNAME set to ''
-    When newgem is executed for project 'my_project' with no options
-    Then file 'Rakefile' is created
-    And does invoke generator 'install_test_unit'
-    And does invoke generator 'install_rubigen_scripts'
-    And does not invoke generator 'install_website'
-    And does not invoke generator 'install_rspec'
-    And does not invoke generator 'install_shoulda'
-    And does not invoke generator 'install_cucumber'
-    And file 'config/website.yml' is not created
-    And output same as contents of 'newgem.out'
+    Given env variable $RUBYFORGE_USERNAME set to ""
+    When newgem is executed for project "my_project" with no options
+    Then file "Rakefile" is created
+    And does invoke generator "install_test_unit"
+    And does invoke generator "install_rubigen_scripts"
+    And does not invoke generator "install_website"
+    And does not invoke generator "install_rspec"
+    And does not invoke generator "install_shoulda"
+    And does not invoke generator "install_cucumber"
+    And file "config/website.yml" is not created
+    And I should see
+      """
+            create  
+            create  doc
+            create  lib
+            create  script
+            create  tasks
+            create  lib/my_project
+            create  History.txt
+            create  Rakefile
+            create  README.rdoc
+            create  PostInstall.txt
+            create  lib/my_project.rb
+        dependency  install_test_unit
+            create    test
+            create    test/test_helper.rb
+            create    test/test_my_project.rb
+        dependency  install_rubigen_scripts
+            exists    script
+            create    script/generate
+            create    script/destroy
+            create  script/console
+            create  Manifest.txt
+            readme  readme
+      Important
+      =========
+
+      * Open Rakefile
+      * Update missing details (gem description, dependent gems, etc.)
+      """
     And Rakefile can display tasks successfully
+    When I invoke task "rake test"
+    Then I should see all 1 tests pass
 
   Scenario: Run newgem with project name containing hypens
     Given a safe folder
-    Given env variable $RUBYFORGE_USERNAME set to ''
-    When newgem is executed for project 'my-project' with no options
+    Given env variable $RUBYFORGE_USERNAME set to ""
+    When newgem is executed for project "my-project" with no options
     Then Rakefile can display tasks successfully
   
   Scenario: Run newgem to include rspec
     Given a safe folder
-    When newgem is executed for project 'my_rspec_project' with options '-T rspec'
-    Then does invoke generator 'install_rspec'
-    And does not invoke generator 'install_test_unit'
-    And does not invoke generator 'install_shoulda'
-    And does not invoke generator 'install_cucumber'
+    When newgem is executed for project "my_rspec_project" with options "-T rspec"
+    Then does invoke generator "install_rspec"
+    And does not invoke generator "install_test_unit"
+    And does not invoke generator "install_shoulda"
+    And does not invoke generator "install_cucumber"
+    And Rakefile can display tasks successfully
+    When I invoke task "rake spec"
+    Then I should see all 1 examples pass
+
+  Scenario: Run newgem to include shoulda
+    Given a safe folder
+    When newgem is executed for project "my_shoulda_project" with options "-T shoulda"
+    Then does invoke generator "install_shoulda"
+    And does not invoke generator "install_test_unit"
+    And does not invoke generator "install_rspec"
+    And does not invoke generator "install_cucumber"
     And Rakefile can display tasks successfully
+    When I invoke task "rake test"
+    Then I should see all 1 tests pass
 
   Scenario: Run newgem to enable website
     Given a safe folder
-    When newgem is executed for project 'my_project' with options '-w'
-    Then does invoke generator 'install_website'
-    And file 'config/website.yml.sample' is created
-    And yaml file 'config/website.yml.sample' contains {"host" => "unknown@rubyforge.org", "remote_dir" => "/var/www/gforge-projects/my_project"}
+    When newgem is executed for project "my_project" with options "-w"
+    Then does invoke generator "install_website"
+    And file "config/website.yml.sample" is created
+    And yaml file "config/website.yml.sample" contains {"host" => "unknown@rubyforge.org", "remote_dir" => "/var/www/gforge-projects/my_project"}
     And Rakefile can display tasks successfully
 
   Scenario: Run newgem to enable website, with env $RUBYFORGE_USERNAME set
     Given a safe folder
-    Given env variable $RUBYFORGE_USERNAME set to 'nicwilliams'
-    When newgem is executed for project 'my_project' with options '-w'
-    Then file 'config/website.yml.sample' is created
-    And yaml file 'config/website.yml.sample' contains {"host" => "nicwilliams@rubyforge.org", "remote_dir" => "/var/www/gforge-projects/my_project"}
+    Given env variable $RUBYFORGE_USERNAME set to "nicwilliams"
+    When newgem is executed for project "my_project" with options "-w"
+    Then file "config/website.yml.sample" is created
+    And yaml file "config/website.yml.sample" contains {"host" => "nicwilliams@rubyforge.org", "remote_dir" => "/var/www/gforge-projects/my_project"}
     And Rakefile can display tasks successfully
 
   Scenario: Run newgem to install misc generators on top of unit test framework
     Given a safe folder
-    When newgem is executed for project 'my_project' with options '-i cucumber'
-    Then does invoke generator 'install_test_unit'
-    And does invoke generator 'install_cucumber'
-    And does not invoke generator 'install_rspec'
+    When newgem is executed for project "my_project" with options "-i cucumber"
+    Then does invoke generator "install_test_unit"
+    And does invoke generator "install_cucumber"
+    And does not invoke generator "install_rspec"
     And Rakefile can display tasks successfully
 
   Scenario: Run newgem to pull in defaults from ~/.newgem.yml file and no argument options
     Given a safe folder
     And ~/.newgem.yml contains {"default" => "-T rspec -i cucumber"}
-    When newgem is executed for project 'my_project' with options ''
-    Then does invoke generator 'install_rspec'
-    And does invoke generator 'install_cucumber'
-    And does not invoke generator 'install_website'
-    And does not invoke generator 'install_test_unit'
+    When newgem is executed for project "my_project" with options ""
+    Then does invoke generator "install_rspec"
+    And does invoke generator "install_cucumber"
+    And does not invoke generator "install_website"
+    And does not invoke generator "install_test_unit"
     And Rakefile can display tasks successfully
 
   Scenario: Run newgem to pull in defaults from ~/.newgem.yml file and merge with runtime args
     Given a safe folder
     And ~/.newgem.yml contains {"default" => "-T rspec -i cucumber"}
-    When newgem is executed for project 'my_project' with options '-i website'
-    Then does invoke generator 'install_rspec'
-    And does invoke generator 'install_cucumber'
-    And does invoke generator 'install_website'
-    And does not invoke generator 'install_test_unit'
+    When newgem is executed for project "my_project" with options "-i website"
+    Then does invoke generator "install_rspec"
+    And does invoke generator "install_cucumber"
+    And does invoke generator "install_website"
+    And does not invoke generator "install_test_unit"
     And Rakefile can display tasks successfully
 
   Scenario: Run newgem and show current version number
     Given a safe folder
-    When newgem is executed only with options '--version'
+    When newgem is executed only with options "--version"
     Then shows version number