aslakhellesoy-cucumber 0.1.16.4 → 0.1.16.5

data/features/cucumber_cli.feature

@@ -1,99 +1,95 @@
 Feature: Cucumber command line
   In order to write better software
   Developers should be able to execute requirements as tests
-  
+
   Scenario: Run single scenario with missing step definition
-    When I run cucumber -q features/sample.feature:3
+    When I run cucumber -q features/sample.feature:5
     Then it should pass with
       """
+      @one
       Feature: Sample
+
+        @two @three
         Scenario: Missing
           Given missing
 
-
       1 scenario
-      1 step pending (1 with no step definition)
-      
+      1 undefined step
+
       """
-      
-  Scenario: Run single failing scenario
-    When I run cucumber -q features/sample.feature:12
+
+  Scenario: Fail with --strict
+    When I run cucumber -q features/sample.feature:5 --strict
     Then it should fail with
       """
+      @one
       Feature: Sample
-        Scenario: Failing
-          Given failing
-            FAIL (RuntimeError)
-            ./features/step_definitions/sample_steps.rb:5:in `Given /^failing$/'
-            features/sample.feature:12:in `Given failing'
 
+        @two @three
+        Scenario: Missing
+          Given missing
 
       1 scenario
-      1 step failed
+      1 undefined step
 
       """
 
-  Scenario: Specify 2 line numbers
-    When I run cucumber -q features/sample.feature:3:12
+  Scenario: Specify 2 line numbers where one is a tag
+    When I run cucumber -q features/sample.feature:5:14
     Then it should fail with
       """
+      @one
       Feature: Sample
+
+        @two @three
         Scenario: Missing
           Given missing
 
+        @four
         Scenario: Failing
           Given failing
             FAIL (RuntimeError)
-            ./features/step_definitions/sample_steps.rb:5:in `Given /^failing$/'
-            features/sample.feature:12:in `Given failing'
-
+            ./features/step_definitions/sample_steps.rb:2:in `flunker'
+            ./features/step_definitions/sample_steps.rb:9:in `/^failing$/'
+            features/sample.feature:16:in `Given failing'
 
       2 scenarios
-      1 step failed
-      1 step pending (1 with no step definition)
+      1 failed step
+      1 undefined step
 
       """
 
-
   Scenario: Require missing step definition from elsewhere
-    When I run cucumber -q -r ../../features/step_definitions/extra_steps.rb features/sample.feature:3
+    When I run cucumber -q -r ../../features/step_definitions/extra_steps.rb features/sample.feature:5
     Then it should pass with
       """
+      @one
       Feature: Sample
+
+        @two @three
         Scenario: Missing
           Given missing
 
-
-      1 scenario
-      1 step passed
-
-      """
-      
-  Scenario: Specify the line number of a blank line
-    When I run cucumber -q features/sample.feature:10
-    Then it should pass with
-      """
-      Feature: Sample
-        Scenario: Passing
-          Given passing
-
-
       1 scenario
-      1 step passed
+      1 passed step
 
       """
 
   Scenario: Specify the line number of a row
-    When I run cucumber -q features/sample.feature:8
+    When I run cucumber -q features/sample.feature:12
     Then it should pass with
       """
+      @one
       Feature: Sample
+
+        @three
         Scenario: Passing
           Given passing
-
+            | a | b |
+            | c | d |
 
       1 scenario
-      1 step passed
+      1 passed step
 
       """
 
@@ -101,19 +97,19 @@ Feature: Cucumber command line
     When I run cucumber -q --format progress features/sample.feature
     Then it should fail with
       """
-      P.F
+      U.F
+
+      (::) failed steps (::)
 
-      Pending Scenarios:
-      
-      1)  Sample (Missing)
-      
-      
-      Failed:
-      
-      1)
-      FAIL
-      ./features/step_definitions/sample_steps.rb:5:in `Given /^failing$/'
-      features/sample.feature:12:in `Given failing'
+      FAIL (RuntimeError)
+      ./features/step_definitions/sample_steps.rb:2:in `flunker'
+      ./features/step_definitions/sample_steps.rb:9:in `/^failing$/'
+      features/sample.feature:16:in `Given failing'
+
+      3 scenarios
+      1 failed step
+      1 undefined step
+      1 passed step
 
       """
 
@@ -126,12 +122,14 @@ Feature: Cucumber command line
         For å slippe å gjøre dumme feil
         Som en regnskapsfører
         Vil jeg kunne legge sammen
+
         Scenario: to tall
           Gitt at jeg har tastet inn 5
           Og at jeg har tastet inn 7
           Når jeg summerer
           Så skal resultatet være 12
 
+        @iterasjon3
         Scenario: tre tall
           Gitt at jeg har tastet inn 5
           Og at jeg har tastet inn 7
@@ -139,85 +137,189 @@ Feature: Cucumber command line
           Når jeg summerer
           Så skal resultatet være 13
 
-
       2 scenarios
-      9 steps passed
+      9 passed steps
 
       """
 
   Scenario: --dry-run
-    When I run cucumber --dry-run features
+    When I run cucumber --dry-run --no-snippets features
     Then it should pass with
       """
-      Feature: Outline Sample  # features/outline_sample.feature
-        Scenario Outline: Test state     # features/outline_sample.feature:3
-          Given <state> without a table  # features/outline_sample.feature:4
+      Feature: Calling undefined step
 
-          |state  |
-          |missing|
-          |passing|
-          |failing|
+        Scenario: Call directly
+          Given a step definition that calls an undefined step
 
-      Feature: Sample  # features/sample.feature
+        Scenario: Call via another
+          Given call step "a step definition that calls an undefined step"
 
-        Scenario: Missing  # features/sample.feature:3
-          Given missing    # other.rb:23
+      Feature: Lots of undefined
 
-        Scenario: Passing  # features/sample.feature:6
-          Given passing    # features/step_definitions/sample_steps.rb:1
+        Scenario: Implement me
+          Given it snows in Sahara
+          Given it's 40 degrees in Norway
+          And it's 40 degrees in Norway
+          When I stop procrastinating
+          And there is world peace
 
-        Scenario: Failing  # features/sample.feature:11
-          Given failing    # features/step_definitions/sample_steps.rb:4
+      Feature: Outline Sample
 
+        Scenario: I have no steps
 
-      7 scenarios
-      6 steps passed
+        Scenario Outline: Test state
+          Given <state> without a table
+          Given <other_state> without a table
+
+        Examples: 
+          | state   | other_state |
+          | missing | passing     |
+          | passing | passing     |
+          | failing | passing     |
+
+      @one
+      Feature: Sample
+
+        @two @three
+        Scenario: Missing
+          Given missing
+
+        @three
+        Scenario: Passing
+          Given passing
+            | a | b |
+            | c | d |
+
+        @four
+        Scenario: Failing
+          Given failing
+
+      10 scenarios
+      9 skipped steps
+      7 undefined steps
 
       """
 
   Scenario: Multiple formatters and outputs
-    When I run cucumber --format progress --out tmp/progress.txt --format html --out tmp/features.html features
-    Then it should fail with
+    When I run cucumber --format progress --out tmp/progress.txt --format pretty --out tmp/pretty.txt  --dry-run features/lots_of_undefined.feature
+    And examples/self_test/tmp/progress.txt should contain
       """
+      UUUUU
+
+      1 scenario
+      5 undefined steps
+
       """
-    And examples/self_test/tmp/progress.txt should contain
+    And examples/self_test/tmp/pretty.txt should match
       """
-      P.FP.F
+      Feature: Lots of undefined
 
-      Pending Scenarios:
+        Scenario: Implement me
+          Given it snows in Sahara
+          Given it's 40 degrees in Norway
+          And it's 40 degrees in Norway
+          When I stop procrastinating
+          And there is world peace
 
-      1)  Outline Sample (Test state)
-      2)  Sample (Missing)
+      1 scenario
+      5 undefined steps
 
+      """
 
-      Failed:
+  Scenario: Run scenario specified by name using --scenario
+    When I run cucumber --scenario Passing -q features
+    Then it should pass with
+      """
+      @one
+      Feature: Sample
 
-      1)
-      FAIL
-      ./features/step_definitions/sample_steps.rb:12:in ` /^failing without a table$/'
-      features/outline_sample.feature:9:in `/^failing without a table$/'
+        @three
+        Scenario: Passing
+          Given passing
+            | a | b |
+            | c | d |
 
-      2)
-      FAIL
-      ./features/step_definitions/sample_steps.rb:5:in `Given /^failing$/'
-      features/sample.feature:12:in `Given failing'
+      1 scenario
+      1 passed step
 
       """
-    And examples/self_test/tmp/features.html should match
+
+  Scenario: Run with a tag that exists on 2 scenarios
+    When I run cucumber -q features --tags three
+    Then it should pass with
       """
-      Given passing
+      @one
+      Feature: Sample
+
+        @two @three
+        Scenario: Missing
+          Given missing
+
+        @three
+        Scenario: Passing
+          Given passing
+            | a | b |
+            | c | d |
+
+      2 scenarios
+      1 undefined step
+      1 passed step
+
       """
-      
-  Scenario: Run scenario specified by name using --scenario
-    When I run cucumber --scenario Passing -q features/sample.feature
-    Then it should pass with
+
+  Scenario: Run with a tag that exists on 1 feature
+    When I run cucumber -q features --tags one
+    Then it should fail with
       """
+      @one
       Feature: Sample
+
+        @two @three
+        Scenario: Missing
+          Given missing
+
+        @three
         Scenario: Passing
           Given passing
+            | a | b |
+            | c | d |
 
+        @four
+        Scenario: Failing
+          Given failing
+            FAIL (RuntimeError)
+            ./features/step_definitions/sample_steps.rb:2:in `flunker'
+            ./features/step_definitions/sample_steps.rb:9:in `/^failing$/'
+            features/sample.feature:16:in `Given failing'
 
-      1 scenario
-      1 step passed
+      3 scenarios
+      1 failed step
+      1 undefined step
+      1 passed step
+
+      """
 
+  Scenario: Reformat files with --autoformat
+    When I run cucumber --autoformat tmp/formatted features
+    Then examples/self_test/tmp/formatted/features/sample.feature should contain
       """
+      @one
+      Feature: Sample
+
+        @two @three
+        Scenario: Missing
+          Given missing
+
+        @three
+        Scenario: Passing
+          Given passing
+            | a | b |
+            | c | d |
+
+        @four
+        Scenario: Failing
+          Given failing
+
+
+      """
+

data/features/cucumber_cli_outlines.feature

@@ -1,54 +1,56 @@
 Feature: Cucumber command line
   In order to write better software
   Developers should be able to execute requirements as tests
-  
-  Scenario: Run scenario outline steps only
-    When I run cucumber -q features/outline_sample.feature:3
-    Then it should pass with
-      """
-      Feature: Outline Sample
-        Scenario Outline: Test state
-          Given <state> without a table
 
-          |state  |
-
-      1 scenario
-    
-      """
-  
-  Scenario: Run single scenario outline table row with missing step definition
+  Scenario: Run scenario outline steps only
     When I run cucumber -q features/outline_sample.feature:7
-    Then it should pass with
+    Then it should fail with
       """
       Feature: Outline Sample
+
         Scenario Outline: Test state
           Given <state> without a table
+          Given <other_state> without a table
 
-          |state  |
-          |missing|
+        Examples: 
+          | state   | other_state |
+          | missing | passing     |
+          | passing | passing     |
+          | failing | passing     |
+            FAIL (RuntimeError)
+            ./features/step_definitions/sample_steps.rb:2:in `flunker'
+            ./features/step_definitions/sample_steps.rb:16:in `/^failing without a table$/'
+            features/outline_sample.feature:12:in `Given failing without a table'
+
+      3 scenarios
+      1 failed step
+      2 skipped steps
+      1 undefined step
+      2 passed steps
 
-      2 scenarios
-      1 step pending (1 with no step definition)
-      
       """
 
   Scenario: Run single failing scenario outline table row
-    When I run cucumber -q features/outline_sample.feature:9
+    When I run cucumber features/outline_sample.feature:12
     Then it should fail with
       """
       Feature: Outline Sample
-        Scenario Outline: Test state
-          Given <state> without a table
 
-          |state  |
-          |failing|
+        Scenario Outline: Test state          # features/outline_sample.feature:5
+          Given <state> without a table
+          Given <other_state> without a table
 
+        Examples: 
+          | state   | other_state |
+          | failing | passing     |
             FAIL (RuntimeError)
-            ./features/step_definitions/sample_steps.rb:12:in ` /^failing without a table$/'
-            features/outline_sample.feature:9:in `/^failing without a table$/'
+            ./features/step_definitions/sample_steps.rb:2:in `flunker'
+            ./features/step_definitions/sample_steps.rb:16:in `/^failing without a table$/'
+            features/outline_sample.feature:12:in `Given failing without a table'
 
-      2 scenarios
-      1 step failed
+      1 scenario
+      1 failed step
+      1 skipped step
 
       """
 
@@ -56,18 +58,24 @@ Feature: Cucumber command line
     When I run cucumber -q --format progress features/outline_sample.feature
     Then it should fail with
       """
-      P.F
+      UUS..FS
 
-      Pending Scenarios:
+      (::) undefined scenarios (::)
 
-      1)  Outline Sample (Test state)
+      features/outline_sample.feature:3:in `Scenario: I have no steps'
 
+      (::) failed steps (::)
 
-      Failed:
+      FAIL (RuntimeError)
+      ./features/step_definitions/sample_steps.rb:2:in `flunker'
+      ./features/step_definitions/sample_steps.rb:16:in `/^failing without a table$/'
+      features/outline_sample.feature:12:in `Given failing without a table'
 
-      1)
-      FAIL
-      ./features/step_definitions/sample_steps.rb:12:in ` /^failing without a table$/'
-      features/outline_sample.feature:9:in `/^failing without a table$/'
+      4 scenarios
+      1 failed step
+      2 skipped steps
+      1 undefined step
+      2 passed steps
 
       """
+

data/features/report_called_undefined_steps.feature

@@ -0,0 +1,31 @@
+Feature: Cucumber command line
+  In order to find out what step definitions need to be implemented
+  Developers should always see what step definition is missing
+
+  Scenario: Get info at arbitrary levels of nesting
+    When I run cucumber features/call_undefined_step_from_step_def.feature
+    Then it should pass with
+      """
+      Feature: Calling undefined step
+
+        Scenario: Call directly                                # features/call_undefined_step_from_step_def.feature:3
+          Given a step definition that calls an undefined step # features/step_definitions/sample_steps.rb:19
+            Undefined step: "this does not exist" (Cucumber::StepMother::Undefined)
+            ./features/step_definitions/sample_steps.rb:20:in `/^a step definition that calls an undefined step$/'
+
+        Scenario: Call via another                                         # features/call_undefined_step_from_step_def.feature:6
+          Given call step "a step definition that calls an undefined step" # features/step_definitions/sample_steps.rb:23
+            Undefined step: "this does not exist" (Cucumber::StepMother::Undefined)
+            ./features/step_definitions/sample_steps.rb:20:in `/^a step definition that calls an undefined step$/'
+
+      2 scenarios
+      2 undefined steps
+
+      You can implement step definitions for missing steps with these snippets:
+
+      Given /^this does not exist$/ do
+      end
+
+
+      """
+

data/features/step_definitions/cucumber_steps.rb

@@ -6,16 +6,20 @@ When /^I run cucumber (.*)$/ do |cmd|
   @dir ||= 'self_test'
   full_dir ||= File.expand_path(File.dirname(__FILE__) + "/../../examples/#{@dir}")
   Dir.chdir(full_dir) do
-    @full_cmd = "#{Cucumber::RUBY_BINARY} #{Cucumber::BINARY} #{cmd}"
+    @full_cmd = "#{Cucumber::RUBY_BINARY} #{Cucumber::BINARY} --no-color #{cmd}"
     @out = `#{@full_cmd}`
     @status = $?.exitstatus
   end
 end
 
 Then /^it should (fail|pass) with$/ do |success, output|
+#puts @out
   @out.should == output
-  code = success == 'fail' ? 1 : 0
-  @status.should == code
+  if success == 'fail'
+    @status.should_not == 0
+  else
+    @status.should == 0
+  end
 end
 
 Then /^(.*) should contain$/ do |file, text|

data/features/step_definitions/extra_steps.rb

@@ -1,2 +1,2 @@
 Given /^missing$/ do
-end
+end

data/features/support/env.rb

@@ -1,7 +1,7 @@
 require 'spec/expectations'
 require 'fileutils'
 
-Before do
+After do
   FileUtils.rm_rf 'examples/self_test/tmp'
   FileUtils.mkdir 'examples/self_test/tmp'
 end

data/gem_tasks/features.rake

@@ -2,5 +2,5 @@ $:.unshift(File.dirname(__FILE__) + '/../lib')
 require 'cucumber/rake/task'
 
 Cucumber::Rake::Task.new do |t|
-  t.cucumber_opts = "--format pretty"
+  t.cucumber_opts = "--format progress"
 end

data/gem_tasks/flog.rake

@@ -1,4 +1,4 @@
 desc "Run flog over significant files"
 task :flog do
-  sh "find lib -name \\*.rb | grep -v feature_..\\.rb | xargs flog"
+  sh "find lib/cucumber -name \\*.rb | grep -v parser\/feature\\.rb | xargs flog"
 end