jwilger-cucumber 0.3.11.200906161550

data/features/cucumber_cli.feature

@@ -0,0 +1,549 @@
+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:5
+    Then it should pass with      
+      """
+      # Feature comment
+      @one
+      Feature: Sample
+
+        @two @three
+        Scenario: Missing
+          Given missing
+
+      1 scenario (1 undefined)
+      1 step (1 undefined)
+
+      """
+
+  Scenario: Fail with --strict
+    When I run cucumber -q features/sample.feature:5 --strict
+    Then it should fail with
+      """
+      # Feature comment
+      @one
+      Feature: Sample
+
+        @two @three
+        Scenario: Missing
+          Given missing
+            Undefined step: "missing" (Cucumber::Undefined)
+            features/sample.feature:7:in `Given missing'
+
+      1 scenario (1 undefined)
+      1 step (1 undefined)
+
+      """
+
+  Scenario: Succeed with --strict
+    When I run cucumber -q features/sample.feature:10 --strict
+    Then it should pass with
+    """
+    # Feature comment
+    @one
+    Feature: Sample
+
+      # Scenario comment
+      @three
+      Scenario: Passing
+        Given passing
+          | a | b |
+          | c | d |
+
+    1 scenario (1 passed)
+    1 step (1 passed)
+
+    """
+
+  @mri186
+  Scenario: Specify 2 line numbers where one is a tag
+    When I run cucumber -q features/sample.feature:5:16
+    Then it should fail with
+      """
+      # Feature comment
+      @one
+      Feature: Sample
+
+        @two @three
+        Scenario: Missing
+          Given missing
+
+        @four
+        Scenario: Failing
+          Given failing
+            \"\"\"
+            hello
+            \"\"\"
+            FAIL (RuntimeError)
+            ./features/step_definitions/sample_steps.rb:2:in `flunker'
+            ./features/step_definitions/sample_steps.rb:9:in `/^failing$/'
+            features/sample.feature:18:in `Given failing'
+      
+      Failing Scenarios:
+      cucumber features/sample.feature:17 # Scenario: Failing
+      
+      2 scenarios (1 failed, 1 undefined)
+      2 steps (1 failed, 1 undefined)
+
+      """
+
+  Scenario: Require missing step definition from elsewhere
+    When I run cucumber -q -r ../../features/step_definitions/extra_steps.rb features/sample.feature:5
+    Then it should pass with
+      """
+      # Feature comment
+      @one
+      Feature: Sample
+
+        @two @three
+        Scenario: Missing
+          Given missing
+
+      1 scenario (1 passed)
+      1 step (1 passed)
+
+      """
+
+  Scenario: Specify the line number of a row
+    When I run cucumber -q features/sample.feature:12
+    Then it should pass with
+      """
+      # Feature comment
+      @one
+      Feature: Sample
+
+        # Scenario comment
+        @three
+        Scenario: Passing
+          Given passing
+            | a | b |
+            | c | d |
+
+      1 scenario (1 passed)
+      1 step (1 passed)
+
+      """
+
+  @mri186
+  Scenario: Run all with progress formatter
+    When I run cucumber -q --format progress features/sample.feature
+    Then it should fail with
+      """
+      U.F
+
+      (::) failed steps (::)
+
+      FAIL (RuntimeError)
+      ./features/step_definitions/sample_steps.rb:2:in `flunker'
+      ./features/step_definitions/sample_steps.rb:9:in `/^failing$/'
+      features/sample.feature:18:in `Given failing'
+
+      Failing Scenarios:
+      cucumber features/sample.feature:17 # Scenario: Failing
+
+      3 scenarios (1 failed, 1 undefined, 1 passed)
+      3 steps (1 failed, 1 undefined, 1 passed)
+
+      """
+
+  Scenario: Run Norwegian
+    Given I am in i18n/no
+    When I run cucumber -q --language no features
+    Then it should pass with
+      """
+      # language: no
+      Egenskap: Summering
+        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
+          Og at jeg har tastet inn 1
+          Når jeg summerer
+          Så skal resultatet være 13
+
+      2 scenarios (2 passed)
+      9 steps (9 passed)
+
+      """
+
+  Scenario: --dry-run
+    When I run cucumber --dry-run --no-snippets features/*.feature --tags ~@lots
+    Then it should pass with
+      """
+      Feature: Calling undefined step
+
+        Scenario: Call directly
+          Given a step definition that calls an undefined step
+
+        Scenario: Call via another
+          Given call step "a step definition that calls an undefined step"
+
+      Feature: Failing expectation
+
+        Scenario: Failing expectation
+          Given failing expectation
+
+      Feature: Lots of undefined
+
+        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
+
+      Feature: multiline
+
+        Background: I'm a multiline name
+          which goes on and on and on for three lines
+          yawn
+          Given passing without a table
+
+        Scenario: I'm a multiline name
+          which goes on and on and on for three lines
+          yawn
+          Given passing without a table
+
+        Scenario Outline: I'm a multiline name
+          which goes on and on and on for three lines
+          yawn
+          Given <state> without a table
+
+          Examples: 
+            | state   |
+            | passing |
+    
+        Scenario Outline: name
+          Given <state> without a table
+
+          Examples: I'm a multiline name
+            which goes on and on and on for three lines
+            yawn
+            | state   |
+            | passing |
+
+      Feature: Outline Sample
+
+        Scenario: I have no steps
+
+        Scenario Outline: Test state
+          Given <state> without a table
+          Given <other_state> without a table
+
+          Examples: Rainbow colours
+            | state   | other_state |
+            | missing | passing     |
+            | passing | passing     |
+            | failing | passing     |
+
+          Examples: Only passing
+            | state   | other_state |
+            | passing | passing     |
+
+      # Feature comment
+      @one
+      Feature: Sample
+
+        @two @three
+        Scenario: Missing
+          Given missing
+
+        # Scenario comment
+        @three
+        Scenario: Passing
+          Given passing
+            | a | b |
+            | c | d |
+
+        @four
+        Scenario: Failing
+          Given failing
+            \"\"\"
+            hello
+            \"\"\"
+
+      Feature: search examples
+
+        Background: Hantu Pisang background match
+          Given passing without a table
+
+        Scenario: should match Hantu Pisang
+          Given passing without a table
+
+        Scenario: Ignore me
+          Given failing without a table
+
+        Scenario Outline: Ignore me
+          Given <state> without a table
+
+          Examples: 
+            | state   |
+            | failing |
+
+        Scenario Outline: Hantu Pisang match
+          Given <state> without a table
+
+          Examples: 
+            | state   |
+            | passing |
+
+        Scenario Outline: no match in name but in examples
+          Given <state> without a table
+
+          Examples: Hantu Pisang
+            | state   |
+            | passing |
+
+          Examples: Ignore me
+            | state   |
+            | failing |
+
+      Feature: undefined multiline args
+      
+        Scenario: pystring
+          Given a pystring
+            \"\"\"
+              example
+            \"\"\"
+      
+        Scenario: table
+          Given a table
+            | table   |
+            | example |
+      
+      23 scenarios (17 skipped, 5 undefined, 1 passed)
+      39 steps (30 skipped, 9 undefined)
+
+      """
+
+  Scenario: Multiple formatters and outputs
+    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 (1 undefined)
+      5 steps (5 undefined)
+
+      """
+    And "examples/self_test/tmp/pretty.txt" should contain
+      """
+      Feature: Lots of undefined
+
+        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 scenario (1 undefined)
+      5 steps (5 undefined)
+
+      """
+
+  Scenario: Run feature elements which matches a name using --name
+    When I run cucumber --name Pisang -q features/
+    Then it should pass with
+      """
+      Feature: search examples
+
+        Background: Hantu Pisang background match
+          Given passing without a table
+
+        Scenario: should match Hantu Pisang
+          Given passing without a table
+
+        Scenario Outline: Hantu Pisang match
+          Given <state> without a table
+
+          Examples: 
+            | state   |
+            | passing |
+
+        Scenario Outline: no match in name but in examples
+          Given <state> without a table
+
+          Examples: Hantu Pisang
+            | state   |
+            | passing |
+
+      3 scenarios (3 passed)
+      6 steps (6 passed)
+
+      """
+
+  Scenario: Run a single background which matches a name using --name (Useful if there is an error in it)
+    When I run cucumber --name 'Hantu Pisang background' -q features/
+    Then it should pass with
+      """
+      Feature: search examples
+
+        Background: Hantu Pisang background match
+          Given passing without a table
+
+      0 scenarios
+      1 step (1 passed)
+
+      """
+
+
+  Scenario: Run with a tag that exists on 2 scenarios
+    When I run cucumber -q features --tags three
+    Then it should pass with
+      """
+      # Feature comment
+      @one
+      Feature: Sample
+
+        @two @three
+        Scenario: Missing
+          Given missing
+
+        # Scenario comment
+        @three
+        Scenario: Passing
+          Given passing
+            | a | b |
+            | c | d |
+
+      2 scenarios (1 undefined, 1 passed)
+      2 steps (1 undefined, 1 passed)
+
+      """
+
+  @mri186
+  Scenario: Run with a tag that exists on 1 feature
+    When I run cucumber -q features --tags one
+    Then it should fail with
+      """
+      # Feature comment
+      @one
+      Feature: Sample
+
+        @two @three
+        Scenario: Missing
+          Given missing
+
+        # Scenario comment
+        @three
+        Scenario: Passing
+          Given passing
+            | a | b |
+            | c | d |
+
+        @four
+        Scenario: Failing
+          Given failing
+            \"\"\"
+            hello
+            \"\"\"
+            FAIL (RuntimeError)
+            ./features/step_definitions/sample_steps.rb:2:in `flunker'
+            ./features/step_definitions/sample_steps.rb:9:in `/^failing$/'
+            features/sample.feature:18:in `Given failing'
+
+      Failing Scenarios:
+      cucumber features/sample.feature:17 # Scenario: Failing
+
+      3 scenarios (1 failed, 1 undefined, 1 passed)
+      3 steps (1 failed, 1 undefined, 1 passed)
+
+      """
+
+  Scenario: Run with a negative tag
+    When I run cucumber -q features/sample.feature --dry-run -t ~four
+    Then it should pass with
+      """
+      # Feature comment
+      @one
+      Feature: Sample
+
+        @two @three
+        Scenario: Missing
+          Given missing
+
+        # Scenario comment
+        @three
+        Scenario: Passing
+          Given passing
+            | a | b |
+            | c | d |
+
+      2 scenarios (1 skipped, 1 undefined)
+      2 steps (1 skipped, 1 undefined)
+
+      """
+
+  Scenario: Reformat files with --autoformat
+    When I run cucumber --autoformat tmp/formatted features
+    Then "examples/self_test/tmp/formatted/features/sample.feature" should contain
+      """
+      # Feature comment
+      @one
+      Feature: Sample
+
+        @two @three
+        Scenario: Missing
+          Given missing
+
+        # Scenario comment
+        @three
+        Scenario: Passing
+          Given passing
+            | a | b |
+            | c | d |
+
+        @four
+        Scenario: Failing
+          Given failing
+            \"\"\"
+            hello
+            \"\"\"
+
+
+      """
+
+  Scenario: Run feature elements which match a name using -n
+    When I run cucumber -n Pisang -q features/
+    Then it should pass with
+      """
+      Feature: search examples
+
+        Background: Hantu Pisang background match
+          Given passing without a table
+
+        Scenario: should match Hantu Pisang
+          Given passing without a table
+
+        Scenario Outline: Hantu Pisang match
+          Given <state> without a table
+
+          Examples: 
+            | state   |
+            | passing |
+
+        Scenario Outline: no match in name but in examples
+          Given <state> without a table
+
+          Examples: Hantu Pisang
+            | state   |
+            | passing |
+
+      3 scenarios (3 passed)
+      6 steps (6 passed)
+
+      """

data/features/cucumber_cli_diff_disabled.feature

@@ -0,0 +1,53 @@
+Feature: Cucumber command line
+  In order to write better software
+  Developers should be able to execute requirements as tests
+
+  @mri186
+  Scenario: Run single failing scenario with default diff enabled
+    When I run cucumber -q features/failing_expectation.feature
+    Then it should fail with
+      """
+      Feature: Failing expectation
+
+        Scenario: Failing expectation
+          Given failing expectation
+            expected: "that",
+                 got: "this" (using ==)
+            Diff:
+            @@ -1,2 +1,2 @@
+            -that
+            +this
+             (Spec::Expectations::ExpectationNotMetError)
+            ./features/step_definitions/sample_steps.rb:63:in `/^failing expectation$/'
+            features/failing_expectation.feature:4:in `Given failing expectation'
+      
+      Failing Scenarios:
+      cucumber features/failing_expectation.feature:3 # Scenario: Failing expectation
+      
+      1 scenario (1 failed)
+      1 step (1 failed)
+
+      """
+
+  @mri186
+  Scenario: Run single failing scenario with diff output disabled
+    When I run cucumber -q --no-diff features/failing_expectation.feature
+    Then it should fail with
+      """
+      Feature: Failing expectation
+
+        Scenario: Failing expectation
+          Given failing expectation
+            expected: "that",
+                 got: "this" (using ==) (Spec::Expectations::ExpectationNotMetError)
+            ./features/step_definitions/sample_steps.rb:63:in `/^failing expectation$/'
+            features/failing_expectation.feature:4:in `Given failing expectation'
+
+      Failing Scenarios:
+      cucumber features/failing_expectation.feature:3 # Scenario: Failing expectation
+      
+      1 scenario (1 failed)
+      1 step (1 failed)
+
+      """
+

data/features/cucumber_cli_outlines.feature

@@ -0,0 +1,109 @@
+Feature: Cucumber command line
+  In order to write better software
+  Developers should be able to execute requirements as tests
+
+  @mri186
+  Scenario: Run scenario outline with filtering on outline name
+    When I run cucumber -q features --name "Test state"
+    Then it should fail with
+      """
+      Feature: Outline Sample
+
+        Scenario Outline: Test state
+          Given <state> without a table
+          Given <other_state> without a table
+
+          Examples: Rainbow colours
+            | 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:6:in `Given <state> without a table'
+
+          Examples: Only passing
+            | state   | other_state |
+            | passing | passing     |
+
+      4 scenarios (1 failed, 1 undefined, 2 passed)
+      8 steps (1 failed, 2 skipped, 1 undefined, 4 passed)
+
+      """
+
+  @mri186
+  Scenario: Run scenario outline steps only
+    When I run cucumber -q features/outline_sample.feature:7
+    Then it should fail with
+      """
+      Feature: Outline Sample
+
+        Scenario Outline: Test state
+          Given <state> without a table
+          Given <other_state> without a table
+
+          Examples: Rainbow colours
+            | 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:6:in `Given <state> without a table'
+
+          Examples: Only passing
+            | state   | other_state |
+            | passing | passing     |
+
+      4 scenarios (1 failed, 1 undefined, 2 passed)
+      8 steps (1 failed, 2 skipped, 1 undefined, 4 passed)
+
+      """
+
+  @mri186
+  Scenario: Run single failing scenario outline table row
+    When I run cucumber features/outline_sample.feature:12
+    Then it should fail with
+      """
+      Feature: Outline Sample
+
+        Scenario Outline: Test state          # features/outline_sample.feature:5
+          Given <state> without a table       # features/step_definitions/sample_steps.rb:15
+          Given <other_state> without a table # features/step_definitions/sample_steps.rb:12
+
+          Examples: Rainbow colours
+            | state   | other_state |
+            | 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:6:in `Given <state> without a table'
+
+      1 scenario (1 failed)
+      2 steps (1 failed, 1 skipped)
+
+      """
+
+  # There are 10 characters in the progress, but only 8 reported steps. Needs investigation.
+  # Looks like we're outputting too many characters.
+  @mri186
+  Scenario: Run all with progress formatter
+    When I run cucumber -q --format progress features/outline_sample.feature
+    Then it should fail with
+      """
+      --U-..F-..
+
+      (::) failed steps (::)
+
+      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:6:in `Given <state> without a table'
+
+      5 scenarios (1 failed, 1 undefined, 3 passed)
+      8 steps (1 failed, 2 skipped, 1 undefined, 4 passed)
+
+      """
+

data/features/custom_formatter.feature

@@ -0,0 +1,11 @@
+Feature: Custom Formatter
+
+  Scenario: count tags
+    When I run cucumber --format Cucumber::Formatter::TagCloud features
+    Then it should fail with
+      """
+      | after_file | background_tagged_before_on_outline | four | lots | one | three | two |
+      | 1          | 1                                   | 1    | 1    | 1   | 2     | 1   |
+
+      """
+