Ambiguity when a step resolves to more than one StepDef at runtime

[bjuric]

Defining two StepDefs like this can lead to the wrong one being called at runtime.

@StepDef
Scenario: I perform <x> on <y>
...

@StepDef
Scenario: I perform <x> on <y> using <z>
...

The following step could be targeted at the first StepDef but could actually result in the second one being called instead of the first one.

When I perform A on B using C

Possible interpretations for the above include:

• <x> = A
• Or either one of the following
• <y> = B and <z> = C (if resolved to 2nd StepDef above)
• <y> = B using C (if resolved to 1st StepDef above)

[bjuric]

Solution will be to detect this condition and raise an error.

[bjuric]

Delivered in gwen v1.3.0 and gwen-web v1.5.0