Example threads. These questions and answers were written by the SDODS team to document real problems and how to fix them. The people named are illustrative, not real users. Questions asked on this site are marked new.
✖ features/cart/cart.feature:41 scenario/duplicate Duplicate scenario title "add an item to the cart" (first at line 12).Line 12 is Scenario: Add an item to the cart and line 41 is Scenario: add an item to the cart . Different capital letter, and the second one has a trailing space. I would not call those the same title. Is this intentional or is the comparison just sloppy?
Accepted answer
Intentional. The comparison trims the title and lowercases it before checking, so capitalisation and surrounding whitespace do not create two scenarios that are the same scenario.
The reason is downstream: the title is the human-facing identity of a test everywhere it appears — the run viewer, the html report, --scenario filtering, flake history keyed by test. Two scenarios whose titles differ only by a capital letter produce a report nobody can read and a flake record split across two rows that are secretly one test.
The message names the line of the first one so you can see them side by side, which usually makes the answer obvious: one of the two is a copy someone forgot to rename.
The check is per feature file, not per project, so the same title in two different files is allowed — Add an item to the cart can exist in cart.feature and in checkout.feature without complaint. Whether that is a good idea is another question, but lint will not stop you.
Also note it counts a Scenario Outline once, by its outline title. The generated example rows get their names from the # title-format: comment and are not compared here.
Wrap commands and output in triple backticks and they will render as a code block.
Checking whether you’re signed in…
Have a different question? Ask it.