[Test Definitions] Warning on duplicated test scenario names #709

Activity

1. tlohmar

   added

   documentationImprovements or additions to documentationImprovements or additions to documentation

   on Sep 14, 2026
2. tlohmar

   changed the title [-]Warning on unique test scenario names[/-] [+][Test Definitions] Warning on duplicated test scenario names[/+] on Sep 14, 2026
3. hdamker commented on Sep 15, 2026

   

   hdamker

   on Sep 15, 2026

   Last edited by hdamker

   Collaborator

   More actions

   @tlohmar I agree that we should document in the Testing Guidelines that the agreed Gherkin linting rules are normative. But that the validation is doing more than the Commonalities agreed guidance is wrong:

   • the rule "no-dupe-scenario-names": ["on", "in-feature"] is configured and enforced since 2024-09-02 (7d06c50), in the meantime moved into the tooling repository. There were no issues or discussion about it since then until the above.
   • It is also a standard rule of Gherkin linters as unique scenario names within a feature file are needed for Cucumber runners and the output identifies a scenario by feature name + scenario name. Dropping the rule is not an option as it would degrade the assets.

   BTW: there are two ways to fix the warnings:

   • make the scenario names unique within the feature file by adding the operation into the scenario name
   • split the .feature file per operation (the scenario names can be reused across features)
4. tlohmar commented on Sep 15, 2026

   

   tlohmar

   on Sep 15, 2026

   ContributorAuthor

   More actions

   Thanks for the clarification.

   Note, the suggestion was not to drop the verification rules. The suggestion was to clarify the Testing Guidelines, so that people are not surprised by the verification warning.

   I can draft a PR, making it clear.