Autocomplete cucumber steps in feature files
- Total 8K
- Win 2K
- OS X 4K
- Linux 2K
|Sep 17||Sep 16||Sep 15||Sep 14||Sep 13||Sep 12||Sep 11||Sep 10||Sep 9||Sep 8||Sep 7||Sep 6||Sep 5||Sep 4||Sep 3||Sep 2||Sep 1||Aug 31||Aug 30||Aug 29||Aug 28||Aug 27||Aug 26||Aug 25||Aug 24||Aug 23||Aug 22||Aug 21||Aug 20||Aug 19||Aug 18||Aug 17||Aug 16||Aug 15||Aug 14||Aug 13||Aug 12||Aug 11||Aug 10||Aug 9||Aug 8||Aug 7||Aug 6||Aug 5||Aug 4|
Sublime plugin to auto complete Cucumber step definitions.
Using Sublime Package Control
If you are using Will Bond's excellent Sublime Package Control, you can easily
install Cucumber Completion via the
Package Control: Install Package menu item.
This package is listed as
Cucumber Completion in the packages list.
While inside the Sublime Packages directory (which is found inside the data directory), clone the repository using:
git clone https://github.com/krockode/sublime-cucumber-completion
Supported Step Definition Formats
Step definitions can be defined in many languages as the cucumber gherkin
language is parsable in various programming languages. The examples
directory contains cucumber step files in different supported formats
which are tested against. The
*.expected files show the completions that will
be generated for sublime projects of these directories.
There are many formats so if you would like a specific flavour implemented please submit an issue for your flavour and/or a pull request with an example in the examples directory of your step definition format.
Cucumber is implemented in many languages and this plugin only supports a couple of implementations. If you would like to see more languages supported, create an issue or submit a pull request.