Scenario Outlines inconsistencies about gherkin HOT 7 OPEN

Checked with @aslakhellesoy and in Gherkin 6 Scenario Outline and Scenario are synonyms - they only differ based on whether they are followed by an Example, so the following are valid:

Scenario Outline: Something
   Given I don't have any examples

Scenario: Something else
    Given <foo>

Examples:
    | foo |
    | bar |

from gherkin.

This would require a BC break here, and in Behat though, as outlines are currently treated differently from scenarios in Behat.

Btw, I'm wondering how cucumber deals with the output formatting for these cases. Does it still tries to output something looking like a colored gherkin file ?

from gherkin.

I don't think it's necessarily a BC break - it allows some new syntaxes (above) that previously would have been a parse error

(our AST would need to still differentiate ScenarioOutline nodes from Scenario nodes, but we could detect which it is based on whether it is followed by Examples)

from gherkin.

ah indeed, if we keep our 2 different nodes based on the presence of Examples, there is no BC break.

from gherkin.

@dpakach As you've been looking at how Examples and Outlines are treated, what do you think about implementing this?

from gherkin.

Just my 2c - the official Gherkin parser does the same - the AST node that gets created depends on the absence/presence of examples. And we managed to release this without any users complaining about BC issues.

from gherkin.

Removing these lines will now produce failing tests

https://github.com/Behat/Gherkin/blob/master/tests/Behat/Gherkin/Cucumber/CompatibilityTest.php#L33-L35

from gherkin.