"and" & "but" keywords should not be handled as dedicated entities about cucumberswift HOT 4 OPEN

Update on this: CucumberSwift v 3.3.6 adds support for using Given, When, or Then to match gherkin that started with And or But. It is scoped appropriately.

EXAMPLE GHERKIN:

Feature description
    Scenario: Description
        Given some precondition
        And some other precondition

EXAMPLE SWIFT:

Given("some other precondition") { _, _ in
    // executes the "And" condition
}

NOTE: By scoped appropriately I mean that this Gherkin will not match Given

Feature description
    Scenario: Description
        And some other precondition

Although because the And/But keywords still exist, they can match that.

from cucumberswift.

I've looked at some other implementations and confirmed that CucumberSwift is not following defined and expected behavior with this. I don't want to create a breaking change if I can avoid it so I'm pondering some implementation decisions.

I'm thinking of doing this over a few releases, to start we can implement the behavior in your example of Given("test123") And still ends up being a dedicated keyword but you start to get some of the desired behavior from the library.

Then we'll play with the * keyword which currently does sort of work for everything, but probably needs to be smarter when it should be treated more like an And.

Then we'll deprecate, but not remove And as an entity outside of the DSL.

At some point later on in life when V4 needs to be a thing we can just remove it altogether.

from cucumberswift.

Hrm, I think you’re right about the behavior of “and” and “but”. Let me look at the spec and some other implementations over the weekend.

If we do implement this feature it’s probably something we would want to approach in the AST where we can enforce an error if there are orphans.

from cucumberswift.

Very nice! 😊

from cucumberswift.