benhamill-gherkin 2.3.5

data/Rakefile

@@ -0,0 +1,19 @@
+# encoding: utf-8
+require 'rubygems'
+require 'bundler'
+unless ENV['RUBY_CC_VERSION']
+  Bundler.setup
+  Bundler::GemHelper.install_tasks
+end
+ENV['RUBYOPT'] = nil # Necessary to prevent Bundler from *&^%$#ing up rake-compiler.
+
+require 'rake/clean'
+
+$:.unshift(File.dirname(__FILE__) + '/lib')
+require 'gherkin/version'
+
+Dir['tasks/**/*.rake'].each { |rake| load File.expand_path(rake) }
+
+task :default  => [:spec, :cucumber]
+task :spec     => defined?(JRUBY_VERSION) ? :jar : :compile
+task :cucumber => defined?(JRUBY_VERSION) ? :jar : :compile

data/VERSION

@@ -0,0 +1 @@
+2.3.5

data/build_native_gems.sh

@@ -0,0 +1,8 @@
+#!/bin/sh
+rm -Rf release
+mkdir release
+GEM_PLATFORM=java gem build gherkin.gemspec
+GEM_PLATFORM=x86-mswin32 gem build gherkin.gemspec
+GEM_PLATFORM=x86-mingw32 gem build gherkin.gemspec
+GEM_PLATFORM=universal-dotnet gem build gherkin.gemspec
+mv *.gem release

data/cucumber.yml

@@ -0,0 +1,3 @@
+default: --format pretty --tags ~@pending,~@wip --strict --color features
+wip: --format pretty --tags @wip --wip features
+pending: --format pretty --tags @pending,~@native_lexer

data/features/escaped_pipes.feature

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

@@ -0,0 +1,237 @@
+# 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

data/features/json_formatter.feature

@@ -0,0 +1,377 @@
+Feature: JSON formatter
+  In order to support greater access to features
+  we want JSON
+
+  Background:
+    Given a JSON formatter
+    And a "ruby" "root" parser
+
+  Scenario: Only a Feature
+    Given the following text is parsed:
+      """
+      # language: no
+      # Another comment
+      Egenskap: Kjapp
+      """
+    Then the outputted JSON should be:
+      """
+      {
+        "comments": [{"value": "# language: no", "line": 1}, {"value": "# Another comment", "line": 2}],
+        "keyword": "Egenskap",
+        "name": "Kjapp",
+        "description": "",
+        "line": 3
+      }
+      """
+
+  Scenario: Feature with scenarios and outlines
+    Given the following text is parsed:
+      """
+      @one
+      Feature: OH HAI
+
+        Scenario: Fujin
+          Given wind
+          Then spirit
+
+        @two
+        Scenario: _why
+          Given chunky
+          Then bacon
+
+        @three @four
+        Scenario Outline: Life
+          Given some <boredom>
+
+        @five
+        Examples: Real life
+          |boredom|
+          |airport|
+          |meeting|
+
+        Scenario: who stole my mojo?
+          When I was
+            |asleep|
+          And so
+            \"\"\"
+            innocent
+            \"\"\"
+
+        # The
+        Scenario Outline: with
+          # all
+          Then nice
+          
+        # comments
+        # everywhere
+        Examples: An example
+          # I mean
+          | partout |
+      """
+    Then the outputted JSON should be:
+      """
+      {
+        "tags": [{"name": "@one", "line":1}],
+        "keyword": "Feature",
+        "name": "OH HAI",
+        "description": "",
+        "line": 2,
+        "elements":[
+          {
+            "type": "scenario",
+            "keyword": "Scenario",
+            "name": "Fujin",
+            "description": "",
+            "line": 4,
+            "steps": [
+              {
+                "keyword": "Given ",
+                "name": "wind",
+                "line": 5
+              },
+              {
+                "keyword": "Then ",
+                "name": "spirit",
+                "line": 6
+              }
+            ]
+          },
+          {
+            "type": "scenario",
+            "tags": [{"name": "@two", "line":8}],
+            "keyword": "Scenario",
+            "name": "_why",
+            "description": "",
+            "line": 9,
+            "steps": [
+              {
+                "keyword": "Given ",
+                "name": "chunky",
+                "line": 10
+              },
+              {
+                "keyword": "Then ",
+                "name": "bacon",
+                "line": 11
+              }
+            ]
+          },
+          {
+            "type": "scenario_outline",
+            "tags": [{"name": "@three", "line":13}, {"name": "@four", "line":13}],
+            "keyword": "Scenario Outline",
+            "name": "Life",
+            "description": "",
+            "line": 14,
+            "steps": [
+              {
+                "keyword": "Given ",
+                "name": "some <boredom>",
+                "line": 15
+              }
+            ],
+            "examples": [
+              {
+                "tags": [{"name": "@five", "line":17}],
+                "keyword": "Examples",
+                "name": "Real life",
+                "description": "",
+                "line": 18,
+                "rows": [
+                  {
+                    "cells": ["boredom"],
+                    "line": 19
+                  },
+                  {
+                    "cells": ["airport"],
+                    "line": 20
+                  },
+                  {
+                    "cells": ["meeting"],
+                    "line": 21
+                  }
+                ]
+              }
+            ]
+          },
+          {
+            "type": "scenario",
+            "keyword": "Scenario",
+            "name": "who stole my mojo?",
+            "description": "",
+            "line": 23,
+            "steps": [
+              {
+                "keyword": "When ",
+                "name": "I was",
+                "line": 24,
+                "multiline_arg": {
+                  "type": "table",
+                  "value": [
+                    {
+                      "line": 25,
+                      "cells": ["asleep"]
+                    }
+                  ]
+                }
+              },
+              {
+                "keyword": "And ",
+                "name": "so",
+                "line": 26,
+                "multiline_arg": {
+                  "type": "py_string",
+                  "value": "innocent",
+                  "line": 27
+                }
+              }
+            ]
+          },
+          {
+            "type": "scenario_outline",
+            "comments": [{"value": "# The", "line":31}],
+            "keyword": "Scenario Outline",
+            "name": "with",
+            "description": "",
+            "line": 32,
+            "steps": [
+              {
+                "comments": [{"value": "# all", "line":33}],
+                "keyword": "Then ",
+                "line": 34,
+                "name": "nice"
+              }
+            ],
+            "examples": [
+              {
+                "comments": [{"value": "# comments", "line": 36}, {"value": "# everywhere", "line": 37}],
+                "keyword": "Examples",
+                "name": "An example",
+                "description": "",
+                "line": 38,
+                "rows": [
+                  {
+                    "comments": [{"value": "# I mean", "line": 39}],
+                    "line": 40,
+                    "cells": ["partout"]
+                  }
+                ]
+              }
+            ]
+          }
+        ]
+      }
+      """
+
+  Scenario:  Feature with Background
+    Given the following text is parsed:
+      """
+      Feature: Kjapp
+
+        Background: No idea what Kjapp means
+          Given I Google it
+
+        # Writing JSON by hand sucks
+        Scenario: 
+          Then I think it means "fast"
+      """
+    Then the outputted JSON should be:
+      """
+      {
+        "keyword": "Feature",
+        "name": "Kjapp",
+        "description": "",
+        "line": 1,
+        "elements": [
+          {
+            "type": "background",
+            "keyword": "Background",
+            "line": 3,
+            "name": "No idea what Kjapp means",
+            "description": "",
+            "steps": [
+              {
+                "keyword": "Given ",
+                "line": 4,
+                "name": "I Google it"
+              }
+            ]
+          },
+          {
+            "type": "scenario",
+            "comments": [{"value": "# Writing JSON by hand sucks", "line": 6}],
+            "keyword": "Scenario",
+            "name": "",
+            "description": "",
+            "line": 7,
+            "steps": [
+              {
+                "keyword": "Then ",
+                "name": "I think it means \"fast\"",
+                "line": 8
+              }
+            ]
+          }
+        ]
+      }
+      """
+  
+  Scenario: Feature with a description
+
+    We want people to be able to put markdown formatting into their descriptions
+    but this means we need to respect whitespace at the start and end of lines
+    in the description.
+    
+    Pay close attention to the whitespace in this example.
+    
+    Given the following text is parsed:
+      """
+      Feature: Foo
+        one line  
+        another line  
+        
+            some pre-formatted stuff
+        
+        Background: name
+            test  
+            test 
+        
+        Scenario: name
+            test  
+            test 
+        
+        Scenario Outline: name
+            test  
+            test 
+          
+          Given <foo> 
+            
+          Examples: name
+              test  
+              test 
+            | foo   |
+            | table |
+      """
+    Then the outputted JSON should be:
+      """
+      {
+        "keyword": "Feature",
+        "name": "Foo",
+        "description": "one line  \nanother line  \n\n    some pre-formatted stuff",
+        "line": 1,
+        "elements": [
+          {
+            "description": "  test  \n  test",
+            "keyword": "Background",
+            "line": 7,
+            "name": "name",
+            "type": "background"
+          },
+          {
+            "description": "  test  \n  test",
+            "keyword": "Scenario",
+            "line": 11,
+            "name": "name",
+            "type": "scenario"
+          },
+          {
+            "description": "  test  \n  test",
+            "examples": [
+              {
+                "description": "  test  \n  test",
+                "keyword": "Examples",
+                "line": 21,
+                "name": "name",
+                "rows": [
+                  {
+                    "cells": [
+                      "foo"
+                    ],
+                    "line": 24
+                  },
+                  {
+                    "cells": [
+                      "table"
+                    ],
+                    "line": 25
+                  }
+                ]
+              }
+            ],
+            "keyword": "Scenario Outline",
+            "line": 15,
+            "name": "name",
+            "steps": [
+              {
+                "keyword": "Given ",
+                "line": 19,
+                "name": "<foo>"
+              }
+            ],
+            "type": "scenario_outline"
+          }
+        ]
+      }
+      """
+
+