Unique Scenario Names for Cuke Linter

[leontraykov]

This pull request adds an additional rule "Unique Scenario Names" to the Cuke_linter to ensure that each scenario within a Cucumber test suite has a unique name.

Functionalities of the Unique Scenario Names Linter:

• The linter checks each scenario, scenario outline, and rule block for unique names within their feature files.
• It handles scenarios and outlines individually and aggregates checks within rules to ensure no duplicates within those contexts.
• For scenario outlines, it generates names based on template examples and verifies each generated name for uniqueness.
• The rule tracks names using a hash map, where keys are file paths, providing a quick lookup to detect duplicates.
• Detected duplicates are reported with the specific location in the feature file, aiding in quick identification and resolution.

# TODO

By default configuration this rule is disabled by default, providing teams the flexibility to enable it based on their specific needs without disrupting existing workflows.

To enable and configure this rule, add the following settings to the linter configuration:

UniqueScenarioNamesLinter:
  Enabled: true
  Level: feature # [suite, feature, rule]

[leoc]

Is this not to be merged?

[enkessler]

@leoc It was marked as a draft and then closed, so I thought that it wasn't ready/the author had changed their mind. I can reopen and finish it up myself in the near future.