21 new rules

Release notes: https://github.com/racodond/sonar-gherkin-plugin/milestone/1?closed=1

• And and But prefixes should be used instead of redundant Given/When/Then prefixes
• Common Given steps should be added to Background
• Examples data table should contain data at least two data rows
• Features should have a name
• Features should have a unique name
• Given steps should follow a regular expression
• Given/When/Then steps should be defined in the right order
• Missing data table columns should be added
• Non-Given steps should be moved out of Background
• Scenarios should define at least one of each Given/When/Then step type
• Scenarios should have a name
• Scenarios should have a unique name
• Step sentences should not be too long
• Steps of unknown type should not be used
• Tags should be defined at the right level
• Tags should not be set on Examples
• Then steps should follow a regular expression
• Unused variables should be removed
• Useless tags should be removed
• When steps should follow a regular expression
• Wording should remain at business level

21 new rules

Release notes: https://github.com/racodond/sonar-gherkin-plugin/milestone/1?closed=1

• And and But prefixes should be used instead of redundant Given/When/Then prefixes
• Common Given steps should be added to Background
• Examples data table should contain data at least two data rows
• Features should have a name
• Features should have a unique name
• Given steps should follow a regular expression
• Given/When/Then steps should be defined in the right order
• Missing data table columns should be added
• Non-Given steps should be moved out of Background
• Scenarios should define at least one of each Given/When/Then step type
• Scenarios should have a name
• Scenarios should have a unique name
• Step sentences should not be too long
• Steps of unknown type should not be used
• Tags should be defined at the right level
• Tags should not be set on Examples
• Then steps should follow a regular expression
• Unused variables should be removed
• Useless tags should be removed
• When steps should follow a regular expression
• Wording should remain at business level

Initial version

This plugin enables scanning of Cucumber Gherkin feature files. It comes with 19 rules and the ability to write your own custom rules.

• Rules provided out of the box:
• "Examples" table should contain data
• "FIXME" tags should be handled
• "TODO" tags should be handled
• All comments should be formatted consistently
• Byte Order Mark (BOM) should not be used for UTF-8 files
• End-line characters should be consistent
• Features should not contain too many scenarios
• Features that do not define any scenario should be removed
• File names should comply with a naming convention
• Files should contain an empty new line at the end
• Files that do not define any feature should be removed
• Lines should not end with trailing whitespaces
• Only tags from the whitelist should be used
• Scenarios should not contain too many steps
• Source code should be properly indented
• Star (*) step prefix should not be used
• Tabulation characters should not be used
• Tags should comply with a naming convention
• Regular expression on comment

Plugin example to write your own custom rules: https://github.com/racodond/sonar-gherkin-custom-rules-plugin

Compatibility: SonarQube 5.6+

Initial version

This plugin enables scanning of Cucumber Gherkin feature files. It comes with 19 rules and the ability to write your own custom rules.

• Rules provided out of the box:
• "Examples" table should contain data
• "FIXME" tags should be handled
• "TODO" tags should be handled
• All comments should be formatted consistently
• Byte Order Mark (BOM) should not be used for UTF-8 files
• End-line characters should be consistent
• Features should not contain too many scenarios
• Features that do not define any scenario should be removed
• File names should comply with a naming convention
• Files should contain an empty new line at the end
• Files that do not define any feature should be removed
• Lines should not end with trailing whitespaces
• Only tags from the whitelist should be used
• Scenarios should not contain too many steps
• Source code should be properly indented
• Star (*) step prefix should not be used
• Tabulation characters should not be used
• Tags should comply with a naming convention
• Regular expression on comment

Plugin example to write your own custom rules: https://github.com/racodond/sonar-gherkin-custom-rules-plugin

Compatibility: SonarQube 5.6+