← All questions

Two Examples blocks, one @smoke and one @regression — lint says found @smoke @regression

@ui
Scenario Outline: Shipping is calculated per country
  Given I am on the checkout page
  When I choose the country "<country>"
  Then the shipping cost should be "<cost>"

  # title-format: <country> → <cost>
  @smoke
  Examples: The two we always check
    | country | cost  |
    | DE      | 4.90  |
    | FR      | 6.50  |

  # title-format: <country> → <cost>
  @regression
  Examples: Everything else
    | country | cost  |
    | ES      | 6.50  |
    | PL      | 7.20  |

✖ features/checkout/shipping.feature:4  tags/suite  Scenario must carry exactly one suite tag (@smoke, @regression, @sanity); found @smoke @regression.

2 answers

• 21votes✓

  Accepted answer

  It is aware of them — that is the problem. Lint builds one tag set per Scenario Outline: the Feature tags, plus the outline's own tags, plus the tags of every Examples: block flattened together. So your outline has @ui @smoke @regression and two suite tags is an error, even though no individual row would ever carry both.

  The rule is checked per outline, not per generated example, so there is no way to express "this table is smoke and that one is regression" on a single outline and have it lint.

  Split it:

  gherkinCopy

  @ui @smoke
  Scenario Outline: Shipping is calculated for the countries we always check
    Given I am on the checkout page
    When I choose the country "<country>"
    Then the shipping cost should be "<cost>"
  
    # title-format: <country> → <cost>
    Examples:
      | country | cost |
      | DE      | 4.90 |
      | FR      | 6.50 |
  
  @ui @regression
  Scenario Outline: Shipping is calculated for the remaining countries
    Given I am on the checkout page
    When I choose the country "<country>"
    Then the shipping cost should be "<cost>"
  
    # title-format: <country> → <cost>
    Examples:
      | country | cost |
      | ES      | 6.50 |
      | PL      | 7.20 |

  Note the two outlines need different titles or you trade the suite error for scenario/duplicate.

  BLanswered by Bea Lindqvist4,318 · 18 Jun 2025
• 12votes

  The flattening is deliberate and it is what makes the useful case work: a tag on one Examples: block that is not a suite tag — @skip:webkit, @mock, @jira:SHOP-42 — is still seen and still validated. Ignoring Examples tags entirely would mean a misspelled @user: on a table went unchecked.

  The cost is your case, where the same merge makes a legal per-table distinction look illegal. Two outlines with a shared Background is the shape we use; the duplication is four lines and it makes the smoke budget visible in the file rather than hidden in a table.

  RNanswered by Reeta Nandalmaintainer41,280 · 20 Jun 2025