cuke_linter 1.3.0 → 1.4.0

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

@@ -1,39 +1,39 @@
-Feature: Feature without scenarios linter
-
-  As a writer of documentation
-  I want features to have at least one use case
-  So that I do not have incomplete documentation
-
-
-  Scenario: Linting (Bad)
-    Given a linter for features without scenarios
-    And the following feature:
-      """
-      Feature:
-      """
-    When it is linted
-    Then an error is reported:
-      | linter                        | problem                  | location         |
-      | FeatureWithoutScenariosLinter | Feature has no scenarios | <path_to_file>:1 |
-
-  Scenario: Linting (Good)
-    Given a linter for features without scenarios
-    And the following feature:
-      """
-      Feature:
-        Scenario:
-      """
-    When it is linted
-    Then no error is reported
-
-  @cuke_modeler_min_version_3
-  Scenario: Linting (Good, with Rules)
-    Given a linter for features without scenarios
-    And the following feature:
-      """
-      Feature:
-        Rule:
-          Scenario:
-      """
-    When it is linted
-    Then no error is reported
+Feature: Feature without scenarios linter
+
+  As a writer of documentation
+  I want features to have at least one use case
+  So that I do not have incomplete documentation
+
+
+  Scenario: Linting (Bad)
+    Given a linter for features without scenarios
+    And the following feature:
+      """
+      Feature:
+      """
+    When it is linted
+    Then an error is reported:
+      | linter                        | problem                  | location         |
+      | FeatureWithoutScenariosLinter | Feature has no scenarios | <path_to_file>:1 |
+
+  Scenario: Linting (Good)
+    Given a linter for features without scenarios
+    And the following feature:
+      """
+      Feature:
+        Scenario:
+      """
+    When it is linted
+    Then no error is reported
+
+  @cuke_modeler_min_version_3
+  Scenario: Linting (Good, with Rules)
+    Given a linter for features without scenarios
+    And the following feature:
+      """
+      Feature:
+        Rule:
+          Scenario:
+      """
+    When it is linted
+    Then no error is reported

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

@@ -1,23 +1,23 @@
-Feature: Outline with single example row linter
-
-  As a writer of documentation
-  I want outlines to have at least two example rows
-  So that I am not needlessly using an outline instead of a scenario
-
-
-  Scenario: Linting
-    Given a linter for outlines with only one example row
-    And the following feature:
-      """
-      Feature:
-
-        Scenario Outline:
-          * a step
-        Examples:
-          | param |
-          | value |
-      """
-    When it is linted
-    Then an error is reported:
-      | linter                            | problem                          | location         |
-      | OutlineWithSingleExampleRowLinter | Outline has only one example row | <path_to_file>:3 |
+Feature: Outline with single example row linter
+
+  As a writer of documentation
+  I want outlines to have at least two example rows
+  So that I am not needlessly using an outline instead of a scenario
+
+
+  Scenario: Linting
+    Given a linter for outlines with only one example row
+    And the following feature:
+      """
+      Feature:
+
+        Scenario Outline:
+          * a step
+        Examples:
+          | param |
+          | value |
+      """
+    When it is linted
+    Then an error is reported:
+      | linter                            | problem                          | location         |
+      | OutlineWithSingleExampleRowLinter | Outline has only one example row | <path_to_file>:3 |

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

@@ -1,24 +1,24 @@
-Feature: Single test background linter
-
-
-  As a writer of documentation
-  I want backgrounds to apply to at least two tests
-  So that I am not needlessly using a background instead of adding the background steps directly to the test
-
-
-  Scenario: Linting
-    Given a linter for backgrounds applied to only one test
-    And the following feature:
-      """
-      Feature:
-
-        Background:
-          * a step
-
-        Scenario:
-          * a step
-      """
-    When it is linted
-    Then an error is reported:
-      | linter                     | problem                            | location         |
-      | SingleTestBackgroundLinter | Background used with only one test | <path_to_file>:3 |
+Feature: Single test background linter
+
+
+  As a writer of documentation
+  I want backgrounds to apply to at least two tests
+  So that I am not needlessly using a background instead of adding the background steps directly to the test
+
+
+  Scenario: Linting
+    Given a linter for backgrounds applied to only one test
+    And the following feature:
+      """
+      Feature:
+
+        Background:
+          * a step
+
+        Scenario:
+          * a step
+      """
+    When it is linted
+    Then an error is reported:
+      | linter                     | problem                            | location         |
+      | SingleTestBackgroundLinter | Background used with only one test | <path_to_file>:3 |

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

@@ -1,43 +1,43 @@
-Feature: Test step with too many characters
-
-  As a reader of documentation
-  I want test steps not to be unduly long
-  So that I can easily understand its purpose
-
-
-  Scenario: Linting
-
-    Given a linter for test steps with too many characters
-    And the following feature:
-      """
-      Feature:
-
-        Scenario:
-          * tea exists and teapots exist and so do cups and saucers and there might be milk in the milk jug together with sugar cubes
-      """
-    When it is linted
-    Then an error is reported:
-      | linter                          | problem                                         | location         |
-      | StepWithTooManyCharactersLinter | Step is too long. 121 characters found (max 80) | <path_to_file>:4 |
-
-
-  Scenario: Configuration of step count threshold
-
-    Given a linter for test steps with too many characters has been registered
-    And the following configuration file:
-      """
-      StepWithTooManyCharactersLinter:
-        StepLengthThreshold: 55
-      """
-    And the following feature:
-      """
-      Feature:
-
-        Scenario:
-          Given that a rose by any other name would still smell as sweet
-      """
-    When the configuration file is loaded
-    And the feature is linted
-    Then an error is reported:
-      | linter                          | problem                                        | location         |
-      | StepWithTooManyCharactersLinter | Step is too long. 56 characters found (max 55) | <path_to_file>:4 |
+Feature: Test step with too many characters
+
+  As a reader of documentation
+  I want test steps not to be unduly long
+  So that I can easily understand its purpose
+
+
+  Scenario: Linting
+
+    Given a linter for test steps with too many characters
+    And the following feature:
+      """
+      Feature:
+
+        Scenario:
+          * tea exists and teapots exist and so do cups and saucers and there might be milk in the milk jug together with sugar cubes
+      """
+    When it is linted
+    Then an error is reported:
+      | linter                          | problem                                         | location         |
+      | StepWithTooManyCharactersLinter | Step is too long. 121 characters found (max 80) | <path_to_file>:4 |
+
+
+  Scenario: Configuration of step count threshold
+
+    Given a linter for test steps with too many characters has been registered
+    And the following configuration file:
+      """
+      StepWithTooManyCharactersLinter:
+        StepLengthThreshold: 55
+      """
+    And the following feature:
+      """
+      Feature:
+
+        Scenario:
+          Given that a rose by any other name would still smell as sweet
+      """
+    When the configuration file is loaded
+    And the feature is linted
+    Then an error is reported:
+      | linter                          | problem                                        | location         |
+      | StepWithTooManyCharactersLinter | Step is too long. 56 characters found (max 55) | <path_to_file>:4 |

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

@@ -1,21 +1,21 @@
-Feature: Step that ends with a period linter
-
-  As a writer of documentation
-  I want to avoid periods at the end of steps
-  So that readability is not impacted when the steps are used in other contexts
-
-
-  Scenario: Linting
-    Given a linter for steps the end with a period
-    And the following feature:
-      """
-      Feature:
-
-        Scenario:
-          * an okay step
-          * a bad step.
-      """
-    When it is linted
-    Then an error is reported:
-      | linter                  | problem                 | location         |
-      | StepWithEndPeriodLinter | Step ends with a period | <path_to_file>:5 |
+Feature: Step that ends with a period linter
+
+  As a writer of documentation
+  I want to avoid periods at the end of steps
+  So that readability is not impacted when the steps are used in other contexts
+
+
+  Scenario: Linting
+    Given a linter for steps the end with a period
+    And the following feature:
+      """
+      Feature:
+
+        Scenario:
+          * an okay step
+          * a bad step.
+      """
+    When it is linted
+    Then an error is reported:
+      | linter                  | problem                 | location         |
+      | StepWithEndPeriodLinter | Step ends with a period | <path_to_file>:5 |

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

@@ -1,41 +1,41 @@
-Feature: Scenario name with too many characters
-
-  As a reader of documentation
-  I want test names not to be unduly long
-  So that I can easily understand its purpose
-
-
-  Scenario: Linter
-
-    Given a linter for test names with too many characters
-    And the following feature:
-      """
-      Feature:
-
-        Scenario: tea exists and teapots exist and so do cups and saucers and there might be milk in the milk jug together with sugar cubes
-      """
-    When it is linted
-    Then an error is reported:
-      | linter                              | problem                                                  | location         |
-      | TestNameWithTooManyCharactersLinter | Scenario name is too long. 121 characters found (max 80) | <path_to_file>:3 |
-
-
-  Scenario: Configuration of test name count threshold
-
-    Given a linter for test names with too many characters has been registered
-    And the following configuration file:
-      """
-      TestNameWithTooManyCharactersLinter:
-        TestNameLengthThreshold: 30
-      """
-    And the following feature:
-      """
-      Feature:
-
-        Scenario: This scenario name is way too long so it would be better to shorten it somehow, please do so
-      """
-    When the configuration file is loaded
-    And the feature is linted
-    Then an error is reported:
-      | linter                              | problem                                                 | location         |
-      | TestNameWithTooManyCharactersLinter | Scenario name is too long. 92 characters found (max 30) | <path_to_file>:3 |
+Feature: Scenario name with too many characters
+
+  As a reader of documentation
+  I want test names not to be unduly long
+  So that I can easily understand its purpose
+
+
+  Scenario: Linter
+
+    Given a linter for test names with too many characters
+    And the following feature:
+      """
+      Feature:
+
+        Scenario: tea exists and teapots exist and so do cups and saucers and there might be milk in the milk jug together with sugar cubes
+      """
+    When it is linted
+    Then an error is reported:
+      | linter                              | problem                                                  | location         |
+      | TestNameWithTooManyCharactersLinter | Scenario name is too long. 121 characters found (max 80) | <path_to_file>:3 |
+
+
+  Scenario: Configuration of test name count threshold
+
+    Given a linter for test names with too many characters has been registered
+    And the following configuration file:
+      """
+      TestNameWithTooManyCharactersLinter:
+        TestNameLengthThreshold: 30
+      """
+    And the following feature:
+      """
+      Feature:
+
+        Scenario: This scenario name is way too long so it would be better to shorten it somehow, please do so
+      """
+    When the configuration file is loaded
+    And the feature is linted
+    Then an error is reported:
+      | linter                              | problem                                                 | location         |
+      | TestNameWithTooManyCharactersLinter | Scenario name is too long. 92 characters found (max 30) | <path_to_file>:3 |

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

@@ -1,29 +1,29 @@
-Feature: Test should use background linter
-
-  As a writer of documentation
-  I want to know if I am including the same steps in every use case
-  So that I can use a background to make it clear that a common context exists
-
-
-  Scenario: Linting
-
-  Note: Also works on outlines.
-
-    Given a linter for tests that should use a background
-    And the following feature:
-      """
-      Feature:
-
-        Scenario:
-          * a common step
-          * a different step
-
-        Scenario:
-          * a common step
-          * a more different step
-      """
-    When it is linted
-    Then an error is reported:
-      | linter                        | problem                                                              | location         |
-      | TestShouldUseBackgroundLinter | Test shares steps with all other tests in feature. Use a background. | <path_to_file>:3 |
-      | TestShouldUseBackgroundLinter | Test shares steps with all other tests in feature. Use a background. | <path_to_file>:7 |
+Feature: Test should use background linter
+
+  As a writer of documentation
+  I want to know if I am including the same steps in every use case
+  So that I can use a background to make it clear that a common context exists
+
+
+  Scenario: Linting
+
+  Note: Also works on outlines.
+
+    Given a linter for tests that should use a background
+    And the following feature:
+      """
+      Feature:
+
+        Scenario:
+          * a common step
+          * a different step
+
+        Scenario:
+          * a common step
+          * a more different step
+      """
+    When it is linted
+    Then an error is reported:
+      | linter                        | problem                                                              | location         |
+      | TestShouldUseBackgroundLinter | Test shares steps with all other tests in feature. Use a background. | <path_to_file>:3 |
+      | TestShouldUseBackgroundLinter | Test shares steps with all other tests in feature. Use a background. | <path_to_file>:7 |

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

@@ -1,50 +1,50 @@
-Feature: Test with action step as final step linter
-
-  As a tester
-  I want to be warned about abnormal step flows
-  So that the tests make sense
-
-
-  Scenario: Linting
-
-  Note: Also works on outlines.
-
-    Given a linter for tests with an action step as the final step
-    And the following feature:
-      """
-      Feature:
-
-        Scenario: Action as final step
-          When the last step
-      """
-    When it is linted
-    Then an error is reported:
-      | linter                              | problem                            | location         |
-      | TestWithActionStepAsFinalStepLinter | Test has 'When' as the final step. | <path_to_file>:3 |
-
-  Scenario: Configuration of keywords for different dialect
-    Given a linter for tests with an action step as the final step has been registered
-    And the following configuration file:
-      """
-      TestWithActionStepAsFinalStepLinter:
-        Given:
-          - Dado
-        When:
-          - Quando
-          - '*'
-        Then:
-          - Então
-      """
-    And the following feature:
-      """
-      # language:pt
-      Funcionalidade: Feature name
-
-        Cenário: scenario name
-          Quando this is an action in pt dialect
-      """
-    When the configuration file is loaded
-    And it is linted
-    Then an error is reported:
-      | linter                              | problem                            | location         |
-      | TestWithActionStepAsFinalStepLinter | Test has 'When' as the final step. | <path_to_file>:4 |
+Feature: Test with action step as final step linter
+
+  As a tester
+  I want to be warned about abnormal step flows
+  So that the tests make sense
+
+
+  Scenario: Linting
+
+  Note: Also works on outlines.
+
+    Given a linter for tests with an action step as the final step
+    And the following feature:
+      """
+      Feature:
+
+        Scenario: Action as final step
+          When the last step
+      """
+    When it is linted
+    Then an error is reported:
+      | linter                              | problem                            | location         |
+      | TestWithActionStepAsFinalStepLinter | Test has 'When' as the final step. | <path_to_file>:3 |
+
+  Scenario: Configuration of keywords for different dialect
+    Given a linter for tests with an action step as the final step has been registered
+    And the following configuration file:
+      """
+      TestWithActionStepAsFinalStepLinter:
+        Given:
+          - Dado
+        When:
+          - Quando
+          - '*'
+        Then:
+          - Então
+      """
+    And the following feature:
+      """
+      # language:pt
+      Funcionalidade: Feature name
+
+        Cenário: scenario name
+          Quando this is an action in pt dialect
+      """
+    When the configuration file is loaded
+    And it is linted
+    Then an error is reported:
+      | linter                              | problem                            | location         |
+      | TestWithActionStepAsFinalStepLinter | Test has 'When' as the final step. | <path_to_file>:4 |

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

@@ -1,29 +1,29 @@
-
-Feature: Tests with bad names are reported
-
-  As a writer of documentation
-  I want to be warned about assertion style scenario names
-  So that I will be able to understand the intent
-
-  Scenario Outline: Flag a test with a bad name
-
-    Note: Also works on outlines.
-
-    Given a linter for tests with bad names
-    And the following feature:
-      """
-      Feature: Bad scenario names
-
-        Scenario: <example_word> scenario name
-          This scenario uses a bad name
-      """
-    When it is linted
-    Then an error is reported:
-      | linter                | problem                                                            | location         |
-      | TestWithBadNameLinter | "Test", "Verify" and "Check" should not be used in scenario names. | <path_to_file>:3 |
-
-  Examples:
-    | example_word |
-    | test         |
-    | verify       |
-    | check        |
+
+Feature: Tests with bad names are reported
+
+  As a writer of documentation
+  I want to be warned about assertion style scenario names
+  So that I will be able to understand the intent
+
+  Scenario Outline: Flag a test with a bad name
+
+    Note: Also works on outlines.
+
+    Given a linter for tests with bad names
+    And the following feature:
+      """
+      Feature: Bad scenario names
+
+        Scenario: <example_word> scenario name
+          This scenario uses a bad name
+      """
+    When it is linted
+    Then an error is reported:
+      | linter                | problem                                                            | location         |
+      | TestWithBadNameLinter | "Test", "Verify" and "Check" should not be used in scenario names. | <path_to_file>:3 |
+
+  Examples:
+    | example_word |
+    | test         |
+    | verify       |
+    | check        |