being consistent and always using bundle exec in the cucumber steps

email-spec · Apr 11, 2012 · 79f3348 · 79f3348
1 parent bcae4c4
commit 79f3348
Showing 1 changed file with 4 additions and 3 deletions.
diff --git a/features/rails3_app.feature b/features/rails3_app.feature
@@ -5,20 +5,21 @@ As a email_spec dev
 I want to verify that the example rails 3 app runs all of it's features as expected
 
   Scenario: generators test
-    When I run "rails g email_spec:steps" in the rails3 app
+    Given the rails3 app is setup with the latest generators
+    When I run "bundle exec rails g email_spec:steps" in the rails3 app
     Then the rails3 app should have the email steps in place
 
   Scenario: regression test
     Given the rails3 app is setup with the latest email steps
-    When I run "rake db:migrate RAILS_ENV=test" in the rails3 app
+    When I run "bundle exec rake db:migrate RAILS_ENV=test" in the rails3 app
     And I run "bundle exec cucumber features -q --no-color" in the rails3 app
     Then I should see the following summary report:
     """
     15 scenarios (7 failed, 8 passed)
     136 steps (7 failed, 1 skipped, 128 passed)
     """
 
-   When I run "rake spec RAILS_ENV=test" in the rails3 app
+   When I run "bundle exec rake spec RAILS_ENV=test" in the rails3 app
    Then I should see the following summary report:
    """
    9 examples, 0 failures