Skip to content
This repository
Browse code

Better scenario names.

  • Loading branch information...
commit 13e70d3282193090865802aedb7f6c18c0b653a2 1 parent 2fc2c90
Gabe Berke-Williams authored January 20, 2012
4  features/generate.feature
... ...
@@ -1,7 +1,7 @@
1 1
 @disable-bundler
2 2
 Feature: Generate bourbon files
3 3
 
4  
-  Scenario: Run `bourbon generate`
  4
+  Scenario: Bourbon generates a new bourbon installation
5 5
     When I generate bourbon files
6 6
     Then the sass directories should have been generated
7 7
     And the following directories should exist:
@@ -11,7 +11,7 @@ Feature: Generate bourbon files
11 11
     And the lib files should have been generated
12 12
     And the output should contain "Bourbon files generated to bourbon/"
13 13
 
14  
-  Scenario: Generator does not overwrite an existing bourbon directory
  14
+  Scenario: Generating does not overwrite an existing bourbon directory
15 15
     Given bourbon is already generated
16 16
     When I generate bourbon files
17 17
     Then the output should contain "Bourbon files already generated, doing nothing."
4  features/update.feature
... ...
@@ -1,7 +1,7 @@
1 1
 @disable-bundler
2 2
 Feature: Update bourbon files
3 3
 
4  
-  Scenario: `bourbon update` updates an existing bourbon install
  4
+  Scenario: Updating updates an existing bourbon install
5 5
     When I generate bourbon files
6 6
     And I write to "bourbon/_bourbon.scss" with:
7 7
       """
@@ -11,7 +11,7 @@ Feature: Update bourbon files
11 11
     Then the output should contain "Bourbon files updated."
12 12
     And the file "bourbon/_bourbon.scss" should not contain "foobar"
13 13
 
14  
-  Scenario: `bourbon update` does not generate a new bourbon install
  14
+  Scenario: Updating does not generate a new bourbon install
15 15
     When I update bourbon files
16 16
     Then bourbon should not have been generated
17 17
     And the output should contain "No existing bourbon installation. Doing nothing."

0 notes on commit 13e70d3

Please sign in to comment.
Something went wrong with that request. Please try again.