Gherkin 3 is a parser and compiler for the Gherkin language.
It is intended to replace Gherkin 2 and be used by
all Cucumber implementations to parse .feature files.
Gherkin 3 is currently implemented for the following platforms:
- .NET (C#)
- JVM (Java)
- JavaScript (Browser or Node.js/IO.js)
- Ruby (MRI, JRuby or any other Ruby implementation)
- Go
- Python
See TODO.md for what's remaining before we're ready to roll it out and refactor
the Cucumber implementations to use it.
See CONTRIBUTING.md if you want to contribute a parser for a new language.
Our wish-list is (in no particular order):
- C
- Perl
- PHP
- Rust
- Swift
// Java
Parser<Feature> parser = new Parser<>(new AstBuilder());
Feature feature = parser.parse(gherkinDoc);// C#
var parser = new Parser();
var feature = parser.Parse(gherkinDoc);# Ruby
require 'gherkin3'
parser = Gherkin3::Parser.new
feature = parser.parse(gherkin_doc)// JavaScript
var Gherkin = require('gherkin');
var parser = new Gherkin.Parser(new Gherkin.AstBuilder());
var gherkinDoc = new Gherkin.TokenScanner(featuresDoc);
var feature = parser.parse(gherkinDoc,new Gherkin.TokenMatcher());// Go
import (
"strings"
"github.com/cucumber/gherkin-go"
)
reader := strings.NewReader(`Feature: ...`)
feature, err := gherkin.ParseFeature(reader)Download the package via: go get github.com/cucumber/gherkin-go
from gherkin3.token_scanner import TokenScanner
from gherkin3.parser import Parser
parser = Parser()
feature = parser.parse(TokenScanner("Feature: Foo"))I wrote up a summary here.
The following diagram outlines the architecture:
╔════════════╗ ┌───────┐ ╔══════╗ ┌──────┐ ╔═══╗
║Feature file║──▶│Scanner│──▶║Tokens║──▶│Parser│──▶║AST║
╚════════════╝ └───────┘ ╚══════╝ └──────┘ ╚═══╝
The scanner reads a gherkin doc (typically read from a .feature file) and creates
a token for each line. The tokens are passed to the parser, which outputs an AST
(Abstract Syntax Tree).
If the scanner sees a # language header, it will reconfigure itself dynamically
to look for Gherkin keywords for the associated language. The keywords are defined in
gherkin-languages.json.
The scanner is hand-written, but the parser is generated by the Berp parser generator as part of the build process.
Berp takes a grammar file (gherkin.berp) and a template file (gherkin-X.razor) as input
and outputs a parser in language X:
╔════════════╗ ┌────────┐ ╔═══════════════╗
║gherkin.berp║──▶│berp.exe│◀──║gherkin-X.razor║
╚════════════╝ └────────┘ ╚═══════════════╝
│
▼
╔════════╗
║Parser.x║
╚════════╝
Also see the wiki for some early design docs (which might be a little outdated, but mostly OK).
The AST produced by the parser can be described with the following class diagram:
Every class represents a node in the AST. Every node has a Location that describes
the line number and column number in the input file. These numbers are 1-indexed.
All fields on nodes are strings (except for Location.line and Location.column).
The implementation is simple objects without behaviour, only data. It's up to the implementation to decide whether to use classes or just basic collections, but the AST must have a JSON representation (this is used for testing).
Each node in the JSON representation also has a type property with the name
of the node type.
You can see some examples in the testdata/good directory.
(Work in progress)
The compiler compiles the AST produced by the parser into a simpler form - Pickles.
╔═══╗ ┌────────┐ ╔═══════╗
║AST║──▶│Compiler│──▶║Pickles║
╚═══╝ └────────┘ ╚═══════╝
The rationale is to decouple Gherkin from Cucumber so that Cucumber is open to support alternative formats to Gherkin (for example Markdown).
The simpler Pickles data structure also simplifies the internals of Cucumber.
Each Scenario will be compiled into a Pickle. A Pickle has a list of
PickleStep, derived from steps in a Scenario.
Each Examples row under Scenario Outline will also be compiled into a Pickle.
Any Background steps will also be compiled into each Pickle.
Tags will be compiled into the Pickle as well (inheriting tags from parent elements
in the Gherkin AST).
Example:
@foo
Feature:
Background:
Given a
Scenario: b
Given c
@bar
Scenario Outline: c
Given <x>
When y
@zap
Examples:
| x |
| d |
| e |This will be compiled into several Pickle objects (here represented as YAML
for simplicity):
- tags:
- @foo
steps:
- text: Given a
- text: Given c
- tags:
- @foo
- @bar
- @zap
steps:
- text: Given a
- text: Given d
- text: When y
- tags:
- @foo
- @bar
- @zap
steps:
- text: Given a
- text: Given e
- text: When y
Each Pickle will also keep a reference back to the original AST nodes for
rendering and error reporting (stack traces).
Cucumber will further transform this list of Pickle to a list of TestCase.
This structure will link runtime information such as Hooks and Step Definitions.
In the short term, the pickle struct definitions will live alongside the Gherkin3 codebase until it settles:
┌─────────┐
┌─────────────┬────────│Cucumber │──────────────┐
│ │ └─────────┘ │
│ │ │ │
│ │ │ │
│ │ │ │
│ │ │ │
┌───────┼─────────────┼─────────────┼───────┐ │
│ │ │ │ │ │
│ ▼ ▼ ▼ │ ▼
│ ┌─────────┐ ┌─────────┐ ┌─────────┐ │ ┌─────────┐
│ │Gherkin3 │ │Gherkin3 │ │ Pickles │ │ │Markdown │
│ │ Parser │ │Compiler │──▶│ │◀─┼──────│Parser / │
│ └─────────┘ └─────────┘ └─────────┘ │ │Compiler │
└───────────────────────────────────────────┘ └─────────┘
Gherkin3 lib
The long term plan is to implement more compilers that can produce Pickles, for
example from Markdown.
When the Pickles/Cucumber seam stabilises we might move Pickles to a separate project. The various compilers producing pickles might move to a separate project too.
See CONTRIBUTING.md