kosmas58-cucumber 0.1.99.22 → 0.1.99.23

data/features/cucumber_cli.feature

@@ -0,0 +1,366 @@
+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
+      """
+      @one
+      Feature: Sample
+
+        @two @three
+        Scenario: Missing
+          Given missing
+
+      1 scenario
+      1 undefined step
+
+      """
+
+  Scenario: Fail with --strict
+    When I run cucumber -q features/sample.feature:5 --strict
+    Then it should fail with
+      """
+      @one
+      Feature: Sample
+
+        @two @three
+        Scenario: Missing
+          Given missing
+            Undefined step: "missing" (Cucumber::Undefined)
+            features/sample.feature:6:in `Given missing'
+
+      1 scenario
+      1 failed step
+
+      """
+
+  Scenario: Succeed with --strict
+    When I run cucumber -q features/sample.feature:9 --strict
+    Then it should pass with
+    """
+    @one
+    Feature: Sample
+
+      @three
+      Scenario: Passing
+        Given passing
+          | a | b |
+          | c | d |
+
+    1 scenario
+    1 passed step
+
+    """
+
+  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
+            \"\"\"
+            hello
+            \"\"\"
+            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'
+
+      2 scenarios
+      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:5
+    Then it should pass with
+      """
+      @one
+      Feature: Sample
+
+        @two @three
+        Scenario: Missing
+          Given missing
+
+      1 scenario
+      1 passed step
+
+      """
+
+  Scenario: Specify the line number of a row
+    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 passed step
+
+      """
+
+  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:16:in `Given failing'
+
+      3 scenarios
+      1 failed step
+      1 undefined step
+      1 passed step
+
+      """
+
+  Scenario: Run Norwegian
+    Given I am in i18n/no
+    When I run cucumber -q --language no features
+    Then it should pass with
+      """
+      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
+      9 passed steps
+
+      """
+
+  Scenario: --dry-run
+    When I run cucumber --dry-run --no-snippets features/*.feature
+    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: 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     |
+
+      @one
+      Feature: Sample
+
+        @two @three
+        Scenario: Missing
+          Given missing
+
+        @three
+        Scenario: Passing
+          Given passing
+            | a | b |
+            | c | d |
+
+        @four
+        Scenario: Failing
+          Given failing
+            \"\"\"
+            hello
+            \"\"\"
+
+      12 scenarios
+      12 skipped steps
+      7 undefined steps
+
+      """
+
+  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
+      5 undefined steps
+
+      """
+    And examples/self_test/tmp/pretty.txt should match
+      """
+      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
+      5 undefined steps
+
+      """
+
+  Scenario: Run scenario specified by name using --scenario
+    When I run cucumber --scenario Passing -q features
+    Then it should pass with
+      """
+      @one
+      Feature: Sample
+
+        @three
+        Scenario: Passing
+          Given passing
+            | a | b |
+            | c | d |
+
+      1 scenario
+      1 passed step
+
+      """
+
+  Scenario: Run with a tag that exists on 2 scenarios
+    When I run cucumber -q features --tags three
+    Then it should pass with
+      """
+      @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 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
+            \"\"\"
+            hello
+            \"\"\"
+            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
+
+      """
+
+  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
+            \"\"\"
+            hello
+            \"\"\"
+
+
+      """
+

data/features/cucumber_cli_diff_disabled.feature

@@ -0,0 +1,45 @@
+Feature: Cucumber command line
+  In order to write better software
+  Developers should be able to execute requirements as tests
+
+  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'
+
+      1 scenario
+      1 failed step
+
+      """
+
+  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'
+
+      1 scenario
+      1 failed step
+
+      """
+

data/features/cucumber_cli_outlines.feature

@@ -0,0 +1,90 @@
+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: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:12:in `Given failing without a table'
+
+        Examples: Only passing
+          | state   | other_state |
+          | passing | passing     |
+
+      4 scenarios
+      1 failed step
+      2 skipped steps
+      1 undefined step
+      4 passed steps
+
+      """
+
+  # The "Only Passing" should not be printed
+  @buggy
+  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:12
+          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:12:in `Given failing without a table'
+
+        Examples: Only passing
+          | state   | other_state |
+
+      1 scenario
+      1 failed step
+      1 skipped step
+
+      """
+
+  Scenario: Run all with progress formatter
+    When I run cucumber -q --format progress features/outline_sample.feature
+    Then it should fail with
+      """
+      UUS..FS..
+
+      (::) undefined scenarios (::)
+
+      features/outline_sample.feature:3:in `Scenario: I have no steps'
+
+      (::) 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:12:in `Given failing without a table'
+
+      5 scenarios
+      1 failed step
+      2 skipped steps
+      1 undefined step
+      4 passed steps
+
+      """
+