gherkin 2.12.2 → 3.2.0

data/features/.cucumber/stepdefs.json

@@ -1,244 +0,0 @@
-[
-  {
-    "file_colon_line": "features/step_definitions/eyeball_steps.rb:1",
-    "flags": "",
-    "source": "^they have arrived$",
-    "steps": [
-      {
-        "args": [
-
-        ],
-        "name": "they have arrived"
-      }
-    ]
-  },
-  {
-    "file_colon_line": "features/step_definitions/gherkin_steps.rb:1",
-    "flags": "",
-    "source": "^a \"(ruby|native)\" \"([^\\\"]*)\" parser$",
-    "steps": [
-
-    ]
-  },
-  {
-    "file_colon_line": "features/step_definitions/gherkin_steps.rb:5",
-    "flags": "",
-    "source": "^the\\ following\\ text\\ is\\ parsed:$",
-    "steps": [
-      {
-        "args": [
-
-        ],
-        "name": "the following text is parsed:"
-      }
-    ]
-  },
-  {
-    "file_colon_line": "features/step_definitions/gherkin_steps.rb:9",
-    "flags": "",
-    "source": "^there\\ should\\ be\\ no\\ parse\\ errors$",
-    "steps": [
-      {
-        "args": [
-
-        ],
-        "name": "there should be no parse errors"
-      }
-    ]
-  },
-  {
-    "file_colon_line": "features/step_definitions/gherkin_steps.rb:13",
-    "flags": "",
-    "source": "^there should be a parse error on (line \\d+)$",
-    "steps": [
-      {
-        "args": [
-          {
-            "offset": 33,
-            "val": "line 1"
-          }
-        ],
-        "name": "there should be a parse error on line 1"
-      }
-    ]
-  },
-  {
-    "file_colon_line": "features/step_definitions/gherkin_steps.rb:17",
-    "flags": "",
-    "source": "^there should be parse errors on (lines .*)$",
-    "steps": [
-      {
-        "args": [
-          {
-            "offset": 32,
-            "val": "lines 1 and 2"
-          }
-        ],
-        "name": "there should be parse errors on lines 1 and 2"
-      },
-      {
-        "args": [
-          {
-            "offset": 32,
-            "val": "lines 1 through 3"
-          }
-        ],
-        "name": "there should be parse errors on lines 1 through 3"
-      },
-      {
-        "args": [
-          {
-            "offset": 32,
-            "val": "lines 10 and 17"
-          }
-        ],
-        "name": "there should be parse errors on lines 10 and 17"
-      },
-      {
-        "args": [
-          {
-            "offset": 32,
-            "val": "lines 3 and 5"
-          }
-        ],
-        "name": "there should be parse errors on lines 3 and 5"
-      },
-      {
-        "args": [
-          {
-            "offset": 32,
-            "val": "lines 5, 10 and 12"
-          }
-        ],
-        "name": "there should be parse errors on lines 5, 10 and 12"
-      }
-    ]
-  },
-  {
-    "file_colon_line": "features/step_definitions/json_formatter_steps.rb:13",
-    "flags": "",
-    "source": "^a JSON formatter$",
-    "steps": [
-
-    ]
-  },
-  {
-    "file_colon_line": "features/step_definitions/json_formatter_steps.rb:18",
-    "flags": "",
-    "source": "^the outputted JSON should be:$",
-    "steps": [
-      {
-        "args": [
-
-        ],
-        "name": "the outputted JSON should be:"
-      }
-    ]
-  },
-  {
-    "file_colon_line": "features/step_definitions/json_parser_steps.rb:6",
-    "flags": "",
-    "source": "^a PrettyFormatter$",
-    "steps": [
-
-    ]
-  },
-  {
-    "file_colon_line": "features/step_definitions/json_parser_steps.rb:11",
-    "flags": "",
-    "source": "^a JSON lexer$",
-    "steps": [
-
-    ]
-  },
-  {
-    "file_colon_line": "features/step_definitions/json_parser_steps.rb:15",
-    "flags": "",
-    "source": "^the following JSON is parsed:$",
-    "steps": [
-      {
-        "args": [
-
-        ],
-        "name": "the following JSON is parsed:"
-      }
-    ]
-  },
-  {
-    "file_colon_line": "features/step_definitions/json_parser_steps.rb:19",
-    "flags": "",
-    "source": "^the outputted text should be:$",
-    "steps": [
-      {
-        "args": [
-
-        ],
-        "name": "the outputted text should be:"
-      }
-    ]
-  },
-  {
-    "file_colon_line": "features/step_definitions/pretty_formatter_steps.rb:50",
-    "flags": "",
-    "source": "^I have Cucumber's source code next to Gherkin's$",
-    "steps": [
-      {
-        "args": [
-
-        ],
-        "name": "I have Cucumber's source code next to Gherkin's"
-      }
-    ]
-  },
-  {
-    "file_colon_line": "features/step_definitions/pretty_formatter_steps.rb:55",
-    "flags": "",
-    "source": "^I find all of the \\.feature files$",
-    "steps": [
-      {
-        "args": [
-
-        ],
-        "name": "I find all of the .feature files"
-      }
-    ]
-  },
-  {
-    "file_colon_line": "features/step_definitions/pretty_formatter_steps.rb:59",
-    "flags": "",
-    "source": "^I send each prettified original through the \"([^\"]*)\" machinery$",
-    "steps": [
-      {
-        "args": [
-          {
-            "offset": 45,
-            "val": "json"
-          }
-        ],
-        "name": "I send each prettified original through the \"json\" machinery"
-      },
-      {
-        "args": [
-          {
-            "offset": 45,
-            "val": "pretty"
-          }
-        ],
-        "name": "I send each prettified original through the \"pretty\" machinery"
-      }
-    ]
-  },
-  {
-    "file_colon_line": "features/step_definitions/pretty_formatter_steps.rb:83",
-    "flags": "",
-    "source": "^the machinery output should be identical to the prettified original$",
-    "steps": [
-      {
-        "args": [
-
-        ],
-        "name": "the machinery output should be identical to the prettified original"
-      }
-    ]
-  }
-]

data/features/escaped_pipes.feature

@@ -1,8 +0,0 @@
-Feature: Escaped pipes
-  Scenario: They are the future
-    Given they have arrived
-      | æ | o |
-      | a | ø |
-    Given they have arrived
-      | æ   | \|o |
-      | \|a | ø\\ |

data/features/feature_parser.feature

@@ -1,237 +0,0 @@
-# language: en
-Feature: Gherkin Feature lexer
-  In order to make it easy to control the Gherkin syntax
-  As a Gherkin developer bent on Gherkin world-domination
-  I want a feature lexer that uses a feature parser to
-  make all the syntax decisions for me
-
-  Background: 
-    Given a "ruby" "root" parser
-
-  Scenario: Correctly formed feature
-    Given the following text is parsed:
-      """
-      # Apologies to Bill Watterson
-      @cardboard_box @wip
-      Feature: Transmogrification
-        As a young boy with a hyperactive imagination
-        I want a cardboard box
-        In order to transform the ennui of suburban life into something
-          befitting my imagination
-        
-        Background: 
-          Given I have a transmogrifier
-          And I am a member of G.R.O.S.S
-      
-        Scenario: Whoozit to whatzit transmogrification
-          Given I have a whoozit
-          When I put it in the transmogrifier
-          And I press the "transmogrify" button
-          Then I should have a whatzit
-      
-        Scenario Outline: Imaginary Beings
-          Given I have a <boring being>
-          When I transmogrify it with the incantation:
-          \"\"\"
-          ALAKAZAM!
-          \"\"\"
-          Then I should have an <exciting being>
-      
-          Examples:
-          | boring being | exciting being |
-          | Sparrow      | Alicanto       |
-          | Goldfish     | Baldanders     |
-          | Cow          | Hsiao          |
-          
-        Scenario: Sense of humor detection
-          Given the following excerpt:
-            \"\"\"
-            WOMAN:  Who are the Britons?
-            ARTHUR:  Well, we all are. we're all Britons and I am your king.
-            WOMAN:  I didn't know we had a king.  I thought we were an autonomous
-                collective.
-            DENNIS:  You're fooling yourself.  We're living in a dictatorship.
-                A self-perpetuating autocracy in which the working classes--
-            WOMAN:  Oh there you go, bringing class into it again.
-            DENNIS:  That's what it's all about if only people would--
-            ARTHUR:  Please, please good people.  I am in haste.  Who lives
-                in that castle?  
-            \"\"\"
-          When I read it
-          Then I should be amused
-      """
-    Then there should be no parse errors
-
-  Scenario: Keyword before feature
-    Given the following text is parsed:
-      """
-      Scenario: Bullying my way to the head of the line
-        Given I am a big bully of a scenario
-        Then I should be caught by the syntax police(y)
-      
-      Feature: Too timid to stand up for myself
-      """
-    Then there should be parse errors on lines 1 through 3
-
-  Scenario: Multiple Features in file
-    Given the following text is parsed:
-      """
-      Feature: 
-        Scenario: Hi
-      Feature: Uh ohs
-        Scenario Outline:
-      Feature: This is silly
-      """
-    Then there should be parse errors on lines 3 and 5
-
-  Scenario: Tag ends background and scenario
-    Given the following text is parsed:
-      """
-      Feature: test feature
-        Background:
-          Given a something
-          @tag
-          And something else
-          
-      @foo
-      Scenario: my scenario
-        @tag
-        Given this is a step
-        @oh_hai
-        And this is a horrible idea
-        Then it shouldn't work
-      """
-    Then there should be parse errors on lines 5, 10 and 12
-
-  Scenario: Malformed Tables
-    Given the following text is parsed:
-      """
-      Feature: Antiques Roadshow
-      Scenario Outline: Table
-        Given a <foo>
-        Then a <bar>        
-        
-      Examples:
-        | foo | bar   |
-        | 42  | towel |
-        @hello
-        | 1   | prime |
-        
-      Scenario: Table arguments
-        Given this step needs this table:
-        | foo | bar |
-        | one | two |
-        @tag
-        | aaa | bbb |
-      """
-    Then there should be parse errors on lines 10 and 17
-
-  Scenario: Well-formed Tables
-    Given the following text is parsed:
-      """
-      Feature: Row-by-row
-      
-      Scenario: Tables with comments!
-        Given I can now comment out a row:
-          | Key  | Value |
-          # | Yes  | No  |
-          # | Good | Bad |
-          | Good | Evil  |
-        Then I am pleased by these things:
-          | Raindrops     | Roses   |
-          # | Whiskers    | Kittens |
-          | Bright Copper | Kettles |
-          # | Warm woolen   | Mittens |
-          | Also Oban | And Hendricks |
-      """
-    Then there should be no parse errors
-
-  Scenario: Multiline keyword descriptions
-    Given the following text is parsed:
-      """
-        Feature: Documentation is fun
-          Scenario Outline: With lots of docs
-            We need lots of embedded documentation for some reason 
-            \"\"\" # Not interpreted as a pystring, just plain text
-            Oh hai
-            \"\"\"
-      
-            La la la
-      
-            Examples:
-            | one | two |
-            | foo | bar |
-      
-            \"\"\"
-            Oh Hello
-            \"\"\"
-      
-            # Body of the scenario outline starts below
-            Given <something> 
-            And something <else>
-      
-            # The real examples table
-            Examples: 
-            | something | else |
-            | orange | apple |
-      """
-    Then there should be no parse errors
-
-  Scenario: Scenario Outline with multiple Example groups
-    Given the following text is parsed:
-      """
-      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     |
-      """
-    Then there should be no parse errors
-
-  Scenario: Multiple Scenario Outlines with multiline outline steps
-    Given the following text is parsed:
-      """
-      Feature: Test
-        Scenario Outline: with step tables
-          Given I have the following fruits in my pantry
-            | name        | quantity |
-            | cucumbers   | 10       |
-            | strawberrys | 5        |
-            | apricots    | 7        |
-      
-          When I eat <number> <fruits> from the pantry
-          Then I should have <left> <fruits> in the pantry
-      
-          Examples:
-            | number | fruits      | left |
-            | 2      | cucumbers   | 8    |
-            | 4      | strawberrys | 1    |
-            | 2      | apricots    | 5    |
-      
-        Scenario Outline: placeholder in a multiline string
-          Given my shopping list
-            \"\"\"
-              Must buy some <fruits>
-            \"\"\"
-          Then my shopping list should equal
-            \"\"\"
-              Must buy some cucumbers
-            \"\"\"
-      
-          Examples:
-            | fruits    |
-            | cucumbers |
-      """
-    Then there should be no parse errors