Same step pattern, different step types are not allowed; additionally step type is ignored in feature files about behat

[stof]

The step type is purely indicative. It does not impact the matching at all.

And changing that would be a BC break so it cannot be done in Behat 3.x.
Note that the step type is also indicative in Cucumber, so the existing behavior is consistent.

[uuf6429]

Thanks for the reply!

From what you say, I think the only course of action is to relax the duplicate/ambiguous step check in cases where the annotations/attributes apply to the exact same step (and in which case it wouldn't be a BC break). Wdyt?

Maybe a naive way of doing it is to run array_unique when extracting all Given/Then/When annotations/attributes patterns of a given step method.

If I get some time, I'll see if I can make this happen.

[stof]

Well, there is strictly no benefit of adding it multiple times on the same method

[uuf6429]

Well, there is strictly no benefit of adding it multiple times on the same method

That is true...in the short term at least.

In my opinion, I still don't like the ambiguity and I would rather have an @Step (if they are all treated equally) or be more strict about Given/When/Then.

The way I see it, there are two ideal cases (as already mentioned) and a middle-ground (which is where we're at), and unfortunately, even that middle-ground is not implemented as expected due to the aforementioned uniqueness problem.