UnderTest.Featurelint VS
Feature/Gherkin linting and style checking for Visual Studio Code
Features
- Executes linters against
*.feature (gherkin) files.
- Current rules are:
- Bad Phrase (phrases which should not be in high quality features)
- Data Table Headers Use Pascal Case
- Ensure feature names are unique
- Ensure scenario names are unique
- Feature name required
- No duplicate tags
- No empty feature files
- No periods at the end of lines
- No
Then s in backgrounds
- No upper case words
- Ensure order of
Given-When-Then
- Scenario name required
- Scenario outline examples should have a name
- Scenario outline should have an example table
- Ensure example elements are mapped rul
Requirements
Installing
- Press Ctrl+Shift+X to open the Extensions tab
- Type
undertest to find the extension
- Click the Install button, then the Enable button
OR
- Open Visual Studio Code
- Press Ctrl+P to open the Quick Open dialog
- Type
ext install undertest.undertest-featurelint to find the extension
- Click the Install button, then the Enable button
OR
- Open a command-line prompt
- Run code --install-extension undertest.undertest-featurelint
Extension Settings
None currently. If you have a request for one, please request.
Changelog
The full changelog is available here: changelog.
Known Issues
Linting is currently limited to single file rules.
| |