kosmas58-cucumber 0.1.99.21 → 0.1.99.22

data/features/background.feature

@@ -1,223 +0,0 @@
-Feature: backgrounds
-  In order to provide a context to my scenarios within a feature
-  As a feature editor
-  I want to write a background section in my features.
-
-  Scenario: run a specific scenario with a background
-    When I run cucumber -q features/background/passing_background.feature:9 --require features
-    Then it should pass with
-    """
-    Feature: Passing background sample
-    
-      Background: 
-        Given '10' cukes
-
-      Scenario: another passing background
-        Then I should have '10' cukes
-
-    1 scenario
-    2 passed steps
-    
-    """
-  
-  Scenario: run a feature with a background that passes
-    When I run cucumber -q features/background/passing_background.feature --require features
-    Then it should pass with
-    """
-    Feature: Passing background sample
-
-      Background: 
-        Given '10' cukes
-
-      Scenario: passing background
-        Then I should have '10' cukes
-
-      Scenario: another passing background
-        Then I should have '10' cukes
-
-    2 scenarios
-    4 passed steps
-    
-    """
-
-  Scenario: run a feature with scenario outlines that has a background that passes
-    When I run cucumber -q features/background/scenario_outline_passing_background.feature --require features
-    Then it should pass with
-    """
-    Feature: Passing background with scenario outlines sample
-
-      Background: 
-        Given '10' cukes
-
-      Scenario Outline: passing background
-        Then I should have '<count>' cukes
-
-      Examples: 
-        | count |
-        | 10    |
-
-      Scenario Outline: another passing background
-        Then I should have '<count>' cukes
-
-      Examples: 
-        | count |
-        | 10    |
-
-    2 scenarios
-    4 passed steps
-
-    """
-
-  Scenario: run a feature with a background that fails
-    When I run cucumber -q features/background/failing_background.feature --require features
-    Then it should fail with
-    """
-    Feature: Failing background sample
-
-      Background: 
-        Given failing without a table
-          FAIL (RuntimeError)
-          ./features/step_definitions/sample_steps.rb:2:in `flunker'
-          ./features/step_definitions/sample_steps.rb:16:in `/^failing without a table$/'
-          features/background/failing_background.feature:4:in `Given failing without a table'
-
-      Scenario: failing background
-        Then I should have '10' cukes
-
-      Scenario: another failing background
-        Then I should have '10' cukes
-
-    2 scenarios
-    2 failed steps
-    2 skipped steps
-
-    """
-
-  Scenario: run a feature with scenario outlines that has a background that fails
-    When I run cucumber -q features/background/scenario_outline_failing_background.feature --require features
-    Then it should fail with
-    """
-    Feature: Failing background with scenario outlines sample
-
-      Background: 
-        Given failing without a table
-          FAIL (RuntimeError)
-          ./features/step_definitions/sample_steps.rb:2:in `flunker'
-          ./features/step_definitions/sample_steps.rb:16:in `/^failing without a table$/'
-          features/background/scenario_outline_failing_background.feature:4:in `Given failing without a table'
-
-      Scenario Outline: failing background
-        Then I should have '<count>' cukes
-
-      Examples: 
-        | count |
-        | 10    |
-
-      Scenario Outline: another failing background
-        Then I should have '<count>' cukes
-
-      Examples: 
-        | count |
-        | 10    |
-
-    2 scenarios
-    2 failed steps
-    2 skipped steps
-
-    """
-
-  Scenario: run a feature with a background that is pending
-    When I run cucumber -q features/background/pending_background.feature --require features
-    Then it should pass with
-    """
-    Feature: Pending background sample
-
-      Background: 
-        Given pending
-
-      Scenario: pending background
-        Then I should have '10' cukes
-
-      Scenario: another pending background
-        Then I should have '10' cukes
-
-    2 scenarios
-    2 skipped steps
-    2 undefined steps
-
-    """
-
-  Scenario: background passes with first scenario but fails with second
-    When I run cucumber -q features/background/failing_background_after_success.feature --require features
-    Then it should fail with
-    """
-    Feature: Failing background after previously successful background sample
-
-      Background: 
-        Given passing without a table
-        And '10' global cukes
-
-      Scenario: passing background
-        Then I should have '10' global cukes
-
-      Background: 
-        Given passing without a table
-        And '10' global cukes
-          FAIL (RuntimeError)
-          ./features/step_definitions/sample_steps.rb:2:in `flunker'
-          ./features/step_definitions/sample_steps.rb:37:in `/^'(.+)' global cukes$/'
-          features/background/failing_background_after_success.feature:3:in `And '10' global cukes'
-
-      Scenario: failing background
-        Then I should have '10' global cukes
-
-    2 scenarios
-    1 failed step
-    1 skipped step
-    4 passed steps
-
-    """
-
-  Scenario: background with multline args
-  When I run cucumber -q features/background/multiline_args_background.feature --require features
-  Then it should pass with
-    """
-    Feature: Passing background with multiline args
-
-      Background: 
-        Given table
-          | a | b |
-          | c | d |
-        And multiline string
-          \"\"\"
-            I'm a cucumber and I'm okay. 
-            I sleep all night and I test all day
-          \"\"\"
-
-      Scenario: passing background
-        Then the table should be
-          | a | b |
-          | c | d |
-        Then the multiline string should be
-          \"\"\"
-            I'm a cucumber and I'm okay. 
-            I sleep all night and I test all day
-          \"\"\"
-
-      Scenario: another passing background
-        Then the table should be
-          | a | b |
-          | c | d |
-        Then the multiline string should be
-          \"\"\"
-            I'm a cucumber and I'm okay. 
-            I sleep all night and I test all day
-          \"\"\"
-
-    2 scenarios
-    8 passed steps
-    
-    """
-
-  @josephwilk
-  Scenario: run a scenario showing explicit background steps --explicit-background

data/features/cucumber_cli.feature

@@ -1,343 +0,0 @@
-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: 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: 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
-            \"\"\"
-
-      11 scenarios
-      11 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_outlines.feature

@@ -1,90 +0,0 @@
-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
-
-      """
-

data/features/custom_formatter.feature

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

data/features/report_called_undefined_steps.feature

@@ -1,32 +0,0 @@
-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::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::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
-        pending
-      end
-
-
-      """
-