When aliasing a step method with table parameter and without, the parameter is not correctly processed if both are used in the same scenario

Description

I have a step method aliased like this (to be able to use the step with table parameters and explicitly as well)

when I now use the steps

the 2nd step gets the variable set from the first step
when the steps are defined in 2 different methods, the behavior is as expected.

Assignee

Unassigned

Reporter

Alexander Lehmann

Labels

None

Components

Affects versions

Priority

Minor
Configure