Package io.cucumber.query

Class NamingStrategy

  • All Implemented Interfaces:
    LineageReducer<String>
    public abstract class NamingStrategy
extends Object
implements LineageReducer<String>
    Names Pickles and other elements in a GherkinDocument.

    Pickles in a Gherkin document have a name. But represented without the structure of a Gherkin document (e.g. in a flat xml report), these names can lose their meaning. The long naming strategy solves this problem by prefixing an elements name with the names of all its ancestors, optionally including the feature name.

    Furthermore, Pickles derived from an example can be named in three ways. Either by their example number (e.g. Example #3.14) or by their pickle name. If a parameterized pickle name is used, a combination of both can be used. 

    
 Feature: Examples Tables
   Scenario Outline: Eating &lt;eat&gt; cucumbers
     Given there are &lt;start&gt; cucumbers
     When I eat &lt;eat&gt; cucumbers
     Then I should have &lt;left&gt; cucumbers

     Examples: These are passing
       | start | eat | left |
       |    12 |   5 |    7 |
       |    20 |   6 |   14 |

     Examples: These are failing
       | start | eat | left |
       |    12 |  20 |    0 |
       |     0 |   1 |    0 |
    With the long strategy, using example numbers and the pickle if parameterized, the pickles in this example would be named:
    • Examples Tables - Eating <eat> cucumbers - These are passing - #1.1: Eating 5 cucumbers
    • Examples Tables - Eating <eat> cucumbers - These are passing - #1.2: Eating 6 cucumbers
    • Examples Tables - Eating <eat> cucumbers - These are failing - #2.1: Eating 20 cucumbers
    • Examples Tables - Eating <eat> cucumbers - These are failing - #2.2: Eating 1 cucumbers

    And with the short strategy, using pickle names:

    • Eating 5 cucumbers
    • Eating 6 cucumbers
    • Eating 20 cucumbers
    • Eating 1 cucumbers