Autocomplete cucumber steps in feature files
- Total 8K
- Win 3K
- Mac 4K
- Linux 2K
|Feb 18||Feb 17||Feb 16||Feb 15||Feb 14||Feb 13||Feb 12||Feb 11||Feb 10||Feb 9||Feb 8||Feb 7||Feb 6||Feb 5||Feb 4||Feb 3||Feb 2||Feb 1||Jan 31||Jan 30||Jan 29||Jan 28||Jan 27||Jan 26||Jan 25||Jan 24||Jan 23||Jan 22||Jan 21||Jan 20||Jan 19||Jan 18||Jan 17||Jan 16||Jan 15||Jan 14||Jan 13||Jan 12||Jan 11||Jan 10||Jan 9||Jan 8||Jan 7||Jan 6||Jan 5|
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.