Tool Support

Several tools recognize Gherkin source (feature files) in a similar way to the Gherkin library itself.

With full i18n support

All of the tools below support all of the i18n translations of the Gherkin grammar.

Editors

• Cucumber TextMate Bundle
  • Code Generator
  • Erb Template
  • Generated Lexer

Syntax highlighters

• Pygments lexer for Gherkin which is used by GitHub and supports all of the i18n languages of Gherkin.
  • Code Generator
  • Erb Template
  • Generated Lexer

Cucumber “cousins”

• Cuke4Duke
  • Code Generator
  • Erb Template
  • Generated Java
  • Erb Template
  • Generated Scala
• Cuke4Nuke
  • Code Generator
  • Erb Template
  • Generated C#

Without full i18n support

These tools don’t (yet) support all of Gherkin’s 40 translations. (It would be easy for their maintainers to make them support it – see Tool Developers below).

Editors

• JetBrains RubyMine – i18n support requested here
• Cuke4Vs – i18n support requested here
• Cucumber Netbeans Plugin – i18n support requested here
• Gherkin Editor – i18n support requested here

Tool Developers

If you’re developing a tool that understands Gherkin, please make it i18n aware. Just look at some of the code generators above. All it takes is a little bit of Ruby/Rake and an Erb template that uses Gherkin::I18n.keyword_regexp to generate a Python, Java, C# or whatever file that is part of your tool.

Some tool developers have built-in handling of fragments like In order to, As a and I want. (This is a common narrative style for feature headers). We recommend that you do not try to recognize or highlight this. People should be feee to choose the wording they want. Moreover, we don’t have translations of those fragments, and even if we did, this style is too prescriptive. Gherkin lets you formulate feature narratives how you want, and so whould related tools.