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