cuke_linter 1.3.0 → 1.4.0

data/testing/cucumber/features/linters/element_with_duplicate_tags.feature

@@ -1,71 +1,71 @@
-Feature: Element with duplicate tags linter
-
-  As a writer of documentation
-  I want taggable elements to not have duplicate of tags
-  So that redundancy is minimized
-
-
-  Scenario: Linting
-
-  Note: Also works on outlines, features, and examples
-
-    Given a linter for elements with duplicate tags
-    And the following feature:
-      """
-      Feature:
-
-        @same_tag @a_different_tag @same_tag
-        Scenario:
-          * a step
-      """
-    When it is linted
-    Then an error is reported:
-      | linter                         | problem                                 | location         |
-      | ElementWithDuplicateTagsLinter | Scenario has duplicate tag '@same_tag'. | <path_to_file>:4 |
-
-
-  Scenario: Configuration of indirect tag inclusion (turned off)
-
-  Note: Tags inherited from other elements are not included by default
-
-    Given a linter for elements with duplicate tags has been registered
-    And the following configuration file:
-      """
-      ElementWithDuplicateTagsLinter:
-        IncludeInheritedTags: false
-      """
-    And the following feature:
-      """
-      @same_tag
-      Feature:
-
-        @same_tag
-        Scenario:
-          * a step
-      """
-    When the configuration file is loaded
-    And it is linted
-    Then no error is reported
-
-
-  Scenario: Configuration of indirect tag inclusion (turned on)
-    Given a linter for elements with duplicate tags has been registered
-    And the following configuration file:
-      """
-      ElementWithDuplicateTagsLinter:
-        IncludeInheritedTags: true
-      """
-    And the following feature:
-      """
-      @same_tag
-      Feature:
-
-        @same_tag
-        Scenario:
-          * a step
-      """
-    When the configuration file is loaded
-    And it is linted
-    Then an error is reported:
-      | linter                         | problem                                 | location         |
-      | ElementWithDuplicateTagsLinter | Scenario has duplicate tag '@same_tag'. | <path_to_file>:5 |
+Feature: Element with duplicate tags linter
+
+  As a writer of documentation
+  I want taggable elements to not have duplicate of tags
+  So that redundancy is minimized
+
+
+  Scenario: Linting
+
+  Note: Also works on outlines, features, and examples
+
+    Given a linter for elements with duplicate tags
+    And the following feature:
+      """
+      Feature:
+
+        @same_tag @a_different_tag @same_tag
+        Scenario:
+          * a step
+      """
+    When it is linted
+    Then an error is reported:
+      | linter                         | problem                                 | location         |
+      | ElementWithDuplicateTagsLinter | Scenario has duplicate tag '@same_tag'. | <path_to_file>:4 |
+
+
+  Scenario: Configuration of indirect tag inclusion (turned off)
+
+  Note: Tags inherited from other elements are not included by default
+
+    Given a linter for elements with duplicate tags has been registered
+    And the following configuration file:
+      """
+      ElementWithDuplicateTagsLinter:
+        IncludeInheritedTags: false
+      """
+    And the following feature:
+      """
+      @same_tag
+      Feature:
+
+        @same_tag
+        Scenario:
+          * a step
+      """
+    When the configuration file is loaded
+    And it is linted
+    Then no error is reported
+
+
+  Scenario: Configuration of indirect tag inclusion (turned on)
+    Given a linter for elements with duplicate tags has been registered
+    And the following configuration file:
+      """
+      ElementWithDuplicateTagsLinter:
+        IncludeInheritedTags: true
+      """
+    And the following feature:
+      """
+      @same_tag
+      Feature:
+
+        @same_tag
+        Scenario:
+          * a step
+      """
+    When the configuration file is loaded
+    And it is linted
+    Then an error is reported:
+      | linter                         | problem                                 | location         |
+      | ElementWithDuplicateTagsLinter | Scenario has duplicate tag '@same_tag'. | <path_to_file>:5 |

data/testing/cucumber/features/linters/element_with_too_many_tags.feature

@@ -1,70 +1,70 @@
-Feature: Element with too many tags linter
-
-  As a reader of documentation
-  I want taggable elements to not have an overabundance of tags
-  So that I can concentrate on the content of the scenario
-
-
-  Scenario: Linting
-
-  Note: Also works on outlines, features, and examples
-  Note: Tags inherited from other elements are not counted by default (see configuration options below)
-
-    Given a linter for elements with too many tags
-    And the following feature:
-      """
-      @this_tag_not_counted
-      Feature:
-
-        @tag_1 @tag_2 @tag_3 @tag_4 @tag_5 @tag_one_too_many
-        Scenario:
-          * a step
-      """
-    When it is linted
-    Then an error is reported:
-      | linter                       | problem                                           | location         |
-      | ElementWithTooManyTagsLinter | Scenario has too many tags. 6 tags found (max 5). | <path_to_file>:5 |
-
-
-  Scenario: Configuration of tag count threshold
-    Given a linter for elements with too many tags has been registered
-    And the following configuration file:
-      """
-      ElementWithTooManyTagsLinter:
-        TagCountThreshold: 3
-      """
-    And the following feature:
-      """
-      Feature:
-
-        @tag_1 @tag_2 @tag_3 @tag_one_too_many
-        Scenario:
-          * a step
-      """
-    When the configuration file is loaded
-    And it is linted
-    Then an error is reported:
-      | linter                       | problem                                           | location         |
-      | ElementWithTooManyTagsLinter | Scenario has too many tags. 4 tags found (max 3). | <path_to_file>:4 |
-
-  Scenario: Configuration of indirect tag count
-    Given a linter for elements with too many tags has been registered
-    And the following configuration file:
-      """
-      ElementWithTooManyTagsLinter:
-        CountInheritedTags: true
-      """
-    And the following feature:
-      """
-      @this_tag_is_also_counted
-      Feature:
-
-        @tag_1 @tag_2 @tag_3 @tag_4 @tag_one_too_many
-        Scenario:
-          * a step
-      """
-    When the configuration file is loaded
-    And it is linted
-    Then an error is reported:
-      | linter                       | problem                                           | location         |
-      | ElementWithTooManyTagsLinter | Scenario has too many tags. 6 tags found (max 5). | <path_to_file>:5 |
+Feature: Element with too many tags linter
+
+  As a reader of documentation
+  I want taggable elements to not have an overabundance of tags
+  So that I can concentrate on the content of the scenario
+
+
+  Scenario: Linting
+
+  Note: Also works on outlines, features, and examples
+  Note: Tags inherited from other elements are not counted by default (see configuration options below)
+
+    Given a linter for elements with too many tags
+    And the following feature:
+      """
+      @this_tag_not_counted
+      Feature:
+
+        @tag_1 @tag_2 @tag_3 @tag_4 @tag_5 @tag_one_too_many
+        Scenario:
+          * a step
+      """
+    When it is linted
+    Then an error is reported:
+      | linter                       | problem                                           | location         |
+      | ElementWithTooManyTagsLinter | Scenario has too many tags. 6 tags found (max 5). | <path_to_file>:5 |
+
+
+  Scenario: Configuration of tag count threshold
+    Given a linter for elements with too many tags has been registered
+    And the following configuration file:
+      """
+      ElementWithTooManyTagsLinter:
+        TagCountThreshold: 3
+      """
+    And the following feature:
+      """
+      Feature:
+
+        @tag_1 @tag_2 @tag_3 @tag_one_too_many
+        Scenario:
+          * a step
+      """
+    When the configuration file is loaded
+    And it is linted
+    Then an error is reported:
+      | linter                       | problem                                           | location         |
+      | ElementWithTooManyTagsLinter | Scenario has too many tags. 4 tags found (max 3). | <path_to_file>:4 |
+
+  Scenario: Configuration of indirect tag count
+    Given a linter for elements with too many tags has been registered
+    And the following configuration file:
+      """
+      ElementWithTooManyTagsLinter:
+        CountInheritedTags: true
+      """
+    And the following feature:
+      """
+      @this_tag_is_also_counted
+      Feature:
+
+        @tag_1 @tag_2 @tag_3 @tag_4 @tag_one_too_many
+        Scenario:
+          * a step
+      """
+    When the configuration file is loaded
+    And it is linted
+    Then an error is reported:
+      | linter                       | problem                                           | location         |
+      | ElementWithTooManyTagsLinter | Scenario has too many tags. 6 tags found (max 5). | <path_to_file>:5 |

data/testing/cucumber/features/linters/example_without_name.feature

@@ -1,34 +1,34 @@
-Feature: Example without name linter
-
-  As a reader of documentation
-  I want every example grouping to have a name
-  So that I can understand the significance of the example data
-
-
-  Scenario: Linting
-    Given a linter for examples without names
-    And the following feature:
-      """
-      Feature:
-
-        Scenario Outline:
-          * a step
-
-        Examples: Happy paths!
-          | param |
-          | value |
-
-        # Unknown paths :(
-        Examples:
-          | param |
-          | value |
-      """
-    When it is linted
-    Then an error is reported:
-      | linter                   | problem                      | location          |
-      | ExampleWithoutNameLinter | Example grouping has no name | <path_to_file>:11 |
-
-  @wip
-  Scenario: Configuration
-
-  Ideas: Configure whether or not the linter triggers on outline with only one Example set?
+Feature: Example without name linter
+
+  As a reader of documentation
+  I want every example grouping to have a name
+  So that I can understand the significance of the example data
+
+
+  Scenario: Linting
+    Given a linter for examples without names
+    And the following feature:
+      """
+      Feature:
+
+        Scenario Outline:
+          * a step
+
+        Examples: Happy paths!
+          | param |
+          | value |
+
+        # Unknown paths :(
+        Examples:
+          | param |
+          | value |
+      """
+    When it is linted
+    Then an error is reported:
+      | linter                   | problem                      | location          |
+      | ExampleWithoutNameLinter | Example grouping has no name | <path_to_file>:11 |
+
+  @wip
+  Scenario: Configuration
+
+  Ideas: Configure whether or not the linter triggers on outline with only one Example set?

data/testing/cucumber/features/linters/feature_file_with_invalid_name.feature

@@ -1,20 +1,20 @@
-Feature: Feature file with invalid name linter
-
-  As a writer of documentation
-  I want to be warned about invalid file names
-  so that I name all features consistently
-
-  Scenario Outline: Linting
-    Given a feature file model named "<name>.feature"
-    And a linter for features with invalid file names
-    When it is linted
-    Then an error is reported:
-      | linter                           | problem                              | location       |
-      | FeatureFileWithInvalidNameLinter | Feature files should be snake_cased. | <path_to_file> |
-
-    Examples: Invalid Names
-      | name    |
-      | Lint    |
-      | lintMe  |
-      | lint me |
-      | lint-me |
+Feature: Feature file with invalid name linter
+
+  As a writer of documentation
+  I want to be warned about invalid file names
+  so that I name all features consistently
+
+  Scenario Outline: Linting
+    Given a feature file model named "<name>.feature"
+    And a linter for features with invalid file names
+    When it is linted
+    Then an error is reported:
+      | linter                           | problem                              | location       |
+      | FeatureFileWithInvalidNameLinter | Feature files should be snake_cased. | <path_to_file> |
+
+    Examples: Invalid Names
+      | name    |
+      | Lint    |
+      | lintMe  |
+      | lint me |
+      | lint-me |

data/testing/cucumber/features/linters/feature_file_with_mismatched_name.feature

@@ -1,32 +1,32 @@
-Feature: Feature file with mismatched name linter
-
-  As a reader of documentation
-  I want file names to match their features
-  so that I can tell what a file is about by reading the name
-
-  Scenario: Linting files with mismatched names
-    Given a feature file model based on the file "some_name" with the following text:
-    """
-    Feature: Some different name
-    """
-    And a linter for features with mismatched file names
-    When it is linted
-    Then an error is reported:
-      | linter                              | problem                                        | location       |
-      | FeatureFileWithMismatchedNameLinter | Feature file name does not match feature name. | <path_to_file> |
-
-  Scenario Outline: Linting files with matching names
-    Given a feature file model based on the file "<file name>" with the following text:
-    """
-    Feature: <feature name>
-    """
-    And a linter for features with mismatched file names
-    When it is linted
-    Then no error is reported
-
-    Examples:
-      | file name             | feature name          |
-      | name_with_underscores | Name with_underscores |
-      | name with spaces      | Name with spaces      |
-      | NameWithCaps          | Name with Caps        |
-      | name-with-hyphens     | Name with-hyphens     |
+Feature: Feature file with mismatched name linter
+
+  As a reader of documentation
+  I want file names to match their features
+  so that I can tell what a file is about by reading the name
+
+  Scenario: Linting files with mismatched names
+    Given a feature file model based on the file "some_name" with the following text:
+    """
+    Feature: Some different name
+    """
+    And a linter for features with mismatched file names
+    When it is linted
+    Then an error is reported:
+      | linter                              | problem                                        | location       |
+      | FeatureFileWithMismatchedNameLinter | Feature file name does not match feature name. | <path_to_file> |
+
+  Scenario Outline: Linting files with matching names
+    Given a feature file model based on the file "<file name>" with the following text:
+    """
+    Feature: <feature name>
+    """
+    And a linter for features with mismatched file names
+    When it is linted
+    Then no error is reported
+
+    Examples:
+      | file name             | feature name          |
+      | name_with_underscores | Name with_underscores |
+      | name with spaces      | Name with spaces      |
+      | NameWithCaps          | Name with Caps        |
+      | name-with-hyphens     | Name with-hyphens     |

data/testing/cucumber/features/linters/feature_with_too_many_different_tags.feature

@@ -1,56 +1,56 @@
-Feature: Feature with too many different tags linter
-
-  As a writer of documentation
-  I want features to not contain too many different tags
-  So that readers do not need to know too many different contexts
-
-
-  Scenario: Linting
-    Given a linter for features with too many different tags
-    And the following feature:
-      """
-      # Total tag count doesn't matter. The count of unique tags is what matters.
-      @tag_A @tag_A @tag_A @tag_A
-      Feature:
-
-        @tag_B @tag_C
-        Scenario:
-          * a step
-
-        @tag_D @tag_E @tag_F @tag_G
-        Scenario:
-          * a step
-
-        @tag_H @tag_I @tag_J
-        Scenario:
-          * a step
-
-        @K
-        Scenario:
-          * a step
-      """
-    When it is linted
-    Then an error is reported:
-      | linter                                | problem                                                           | location         |
-      | FeatureWithTooManyDifferentTagsLinter | Feature contains too many different tags. 11 tags found (max 10). | <path_to_file>:3 |
-
-  Scenario: Configuration of tag count threshold
-    Given a linter for features with too many different tags has been registered
-    And the following configuration file:
-      """
-      FeatureWithTooManyDifferentTagsLinter:
-        TagCountThreshold: 2
-      """
-    And the following feature:
-      """
-      @tag_A @tag_B @tag_C
-      Feature:
-
-        Scenario:
-          * a step
-      """
-    When the configuration file is loaded
-    And it is linted
-    Then an error is reported:
-      | linter                                | problem                                                         | location         |
-      | FeatureWithTooManyDifferentTagsLinter | Feature contains too many different tags. 3 tags found (max 2). | <path_to_file>:2 |
+Feature: Feature with too many different tags linter
+
+  As a writer of documentation
+  I want features to not contain too many different tags
+  So that readers do not need to know too many different contexts
+
+
+  Scenario: Linting
+    Given a linter for features with too many different tags
+    And the following feature:
+      """
+      # Total tag count doesn't matter. The count of unique tags is what matters.
+      @tag_A @tag_A @tag_A @tag_A
+      Feature:
+
+        @tag_B @tag_C
+        Scenario:
+          * a step
+
+        @tag_D @tag_E @tag_F @tag_G
+        Scenario:
+          * a step
+
+        @tag_H @tag_I @tag_J
+        Scenario:
+          * a step
+
+        @K
+        Scenario:
+          * a step
+      """
+    When it is linted
+    Then an error is reported:
+      | linter                                | problem                                                           | location         |
+      | FeatureWithTooManyDifferentTagsLinter | Feature contains too many different tags. 11 tags found (max 10). | <path_to_file>:3 |
+
+  Scenario: Configuration of tag count threshold
+    Given a linter for features with too many different tags has been registered
+    And the following configuration file:
+      """
+      FeatureWithTooManyDifferentTagsLinter:
+        TagCountThreshold: 2
+      """
+    And the following feature:
+      """
+      @tag_A @tag_B @tag_C
+      Feature:
+
+        Scenario:
+          * a step
+      """
+    When the configuration file is loaded
+    And it is linted
+    Then an error is reported:
+      | linter                                | problem                                                         | location         |
+      | FeatureWithTooManyDifferentTagsLinter | Feature contains too many different tags. 3 tags found (max 2). | <path_to_file>:2 |

data/testing/cucumber/features/linters/feature_without_description.feature

@@ -1,17 +1,17 @@
-Feature: Feature without description linter
-
-  As a writer of documentation
-  I want features to have a description
-  So that I do not have incomplete documentation
-
-
-  Scenario: Linting
-    Given a linter for features without a description
-    And the following feature:
-      """
-      Feature: Features must have a description
-      """
-    When it is linted
-    Then an error is reported:
-      | linter                          | problem                    | location         |
-      | FeatureWithoutDescriptionLinter | Feature has no description | <path_to_file>:1 |
+Feature: Feature without description linter
+
+  As a writer of documentation
+  I want features to have a description
+  So that I do not have incomplete documentation
+
+
+  Scenario: Linting
+    Given a linter for features without a description
+    And the following feature:
+      """
+      Feature: Features must have a description
+      """
+    When it is linted
+    Then an error is reported:
+      | linter                          | problem                    | location         |
+      | FeatureWithoutDescriptionLinter | Feature has no description | <path_to_file>:1 |

data/testing/cucumber/features/linters/feature_without_name.feature

@@ -1,18 +1,18 @@
-Feature: Feature without name linter
-
-  As a reader of documentation
-  I want every feature to have a name
-  So that I can get an idea of  what the feature is about without having to read every use case
-
-
-  Scenario: Linting
-    Given a linter for features without a name
-    And the following feature:
-      """
-      Feature:
-        This feature does not have a name
-      """
-    When it is linted
-    Then an error is reported:
-      | linter                   | problem                       | location         |
-      | FeatureWithoutNameLinter | Feature does not have a name. | <path_to_file>:1 |
+Feature: Feature without name linter
+
+  As a reader of documentation
+  I want every feature to have a name
+  So that I can get an idea of  what the feature is about without having to read every use case
+
+
+  Scenario: Linting
+    Given a linter for features without a name
+    And the following feature:
+      """
+      Feature:
+        This feature does not have a name
+      """
+    When it is linted
+    Then an error is reported:
+      | linter                   | problem                       | location         |
+      | FeatureWithoutNameLinter | Feature does not have a name. | <path_to_file>:1 |