gherkin 0.0.4-i386-mswin32

data/.gitignore

@@ -0,0 +1,7 @@
+*.sw?
+.DS_Store
+coverage
+rdoc
+pkg
+ext
+tmp

data/LICENSE

@@ -0,0 +1,20 @@
+Copyright (c) 2009 Mike Sassak, Gregory Hnatiuk, Aslak Hellesøy
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/README.rdoc

@@ -0,0 +1,66 @@
+= Gherkin
+
+Fast Gherkin lexer based on Ragel. 
+
+Gherkin is the language that has evolved out of the Cucumber project. Cucumber currently uses
+Treetop, which is too slow for larger projects.
+
+This project will *not* include code to build an AST. Instead, this lexer will have an API
+that makes it possible to plug in a builder that can build an AST.
+
+== Testing
+
+rake ragel
+rake spec cucumber
+
+== Cleaning generated code
+
+rake clobber
+
+== Release process
+
+Run just "rake" for each platform (1.8.6, 1.8.7, 1.9, jruby) to make sure all is green.
+
+1) Bump version in the VERSION file
+2) rake gemspec
+3) Commit everything
+4) rake release
+5) ./nativegems.sh
+6) gem push pkg/... (for each native gem)
+
+TODO: Also build windows gem with dll using rake-compiler. MinGW gem can be done on OS X/Linux, but
+the one for the old Ruby one-click installers must be built with Visual Studio/nmake.
+
+== Build windows gems on OS X
+
+* http://www.copiousfreetime.org/articles/2008/10/12/building-gems-for-windows.html
+* rake-compiler docs
+
+== Notes
+
+Ragel supports Ruby, but it's much slower than C. The ruby target will be used for development.
+The final version will use C for MRI and Java for JRuby.
+
+== Ragel links
+
+* http://www.complang.org/ragel/
+* http://dev.sipdoc.net/attachments/2/ragel_talk.pdf 
+* http://lambda-the-ultimate.org/node/1125
+* http://www.zedshaw.com/essays/ragel_state_charts.html
+* http://www.devchix.com/2008/01/13/a-hello-world-for-ruby-on-ragel-60/
+
+== Note on Patches/Pull Requests
+ 
+* Fork the project.
+* Run rake ragel:rb to generate all the I18N lexers
+* Make your feature addition or bug fix.
+* Add tests for it. This is important so I don't break it in a
+  future version unintentionally.
+* Commit, do not mess with rakefile, version, or history.
+  (if you want to have your own version, that is fine but
+   bump version in a commit by itself I can ignore when I pull)
+* Send me a pull request. Bonus points for topic branches.
+
+== Copyright
+
+Copyright (c) 2009 Mike Sassak, Gregory Hnatiuk, Aslak Hellesøy. See LICENSE for details.

data/Rakefile

@@ -0,0 +1,49 @@
+# encoding: utf-8
+require 'rbconfig'
+require 'rubygems'
+require 'rake'
+require 'rake/clean'
+
+begin
+  require 'jeweler'
+  Jeweler::Tasks.new do |gem|
+    gem.name = "gherkin"
+    gem.summary = %Q{Fast Gherkin lexer}
+    gem.description = %Q{A fast Gherkin lexer in Ragel}
+    gem.email = "cukes@googlegroups.com"
+    gem.homepage = "http://github.com/aslakhellesoy/gherkin"
+    gem.authors = ["Mike Sassak", "Gregory Hnatiuk", "Aslak Hellesøy"]
+    gem.executables = ["gherkin"]
+    gem.add_development_dependency "rspec", "1.2.9"
+    gem.add_development_dependency "cucumber", "0.4.4"
+    gem.add_development_dependency "rake-compiler", "0.6.0" unless defined?(JRUBY_VERSION)
+    
+    case ENV['PLATFORM']
+    when 'universal-java-1.5'
+      gem.platform = 'universal-java-1.5'
+      gem.files += FileList['lib/gherkin.jar']
+      gem.extensions = []
+    when 'i386-mswin32'
+      gem.platform = 'i386-mswin32'
+      gem.files += FileList['lib/*.so']
+      gem.extensions = []
+    when 'i386-mingw32'
+      gem.platform = 'i386-mingw32'
+      gem.files += FileList['lib/*.so']
+      gem.extensions = []
+    else
+      gem.files += FileList['lib/gherkin/rb_lexer/*.rb']
+      gem.files += FileList['ext/**/*.c']
+      gem.extensions = FileList['ext/**/extconf.rb']
+    end
+    
+    # gem is a Gem::Specification... see http://www.rubygems.org/read/chapter/20 for additional settings
+  end
+  Jeweler::GemcutterTasks.new
+rescue LoadError
+  puts "Jeweler (or a dependency) not available. Install it with: sudo gem install jeweler"
+end
+
+Dir['tasks/**/*.rake'].each { |rake| load rake }
+
+task :default => [:jar, :compile, :spec, :cucumber]

data/VERSION.yml

@@ -0,0 +1,4 @@
+--- 
+:minor: 0
+:patch: 4
+:major: 0

data/bin/gherkin

@@ -0,0 +1,10 @@
+#!/usr/bin/env ruby
+$:.unshift(File.dirname(__FILE__) + '/../lib') unless $:.include?(File.dirname(__FILE__) + '/../lib')
+
+require 'gherkin'
+require 'gherkin/tools/pretty_printer'
+
+listener = Gherkin::Tools::PrettyPrinter.new(STDOUT)
+parser = Gherkin::Parser.new(listener, true) # We could skip the parser here, if we don't want to verify well-formedness
+lexer = Gherkin::I18nLexer.new(parser)
+lexer.scan(IO.read(ARGV[0]))

data/cucumber.yml

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

data/features/feature_parser.feature

@@ -0,0 +1,206 @@
+# 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 "en", "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: 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: 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: 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/native_lexer.feature

@@ -0,0 +1,19 @@
+Feature: Native (C/Java) Lexer
+
+  Background:
+    Given a "en", "native" "root" parser
+
+  Scenario: Parsing an empty feature
+    Given the following text is parsed:
+      """
+      Feature: blah
+      """
+    Then there should be no parse errors
+  
+  Scenario: Parsing a comment
+    Given the following text is parsed:
+      """
+      # A comment
+      Feature: Hello
+      """
+    Then there should be no parse errors

data/features/parser_with_native_lexer.feature

@@ -0,0 +1,205 @@
+Feature: Gherkin Feature lexer/parser
+  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 "en", "native" "root" parser
+
+  Scenario: Correctly formed feature
+    When 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
+    When 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: Tag ends background and scenario
+    When 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: Tables
+    When 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: Multiline keyword descriptions
+    When 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
+    When 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
+    When 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