[jbehave-dev] [jira] (JBEHAVE-800) When aliasing a step method with table parameter and without, the parameter is not correctly processed if both are used in the same scenario

[Mauro Talevi (JIRA)]

Mauro Talevi commented on JBEHAVE-800 When aliasing a step method with table parameter and without, the parameter is not correctly processed if both are used in the same scenario Hi Alex, when you have a parametrised scenario, the named parameters in the examples tables values will override any value parsed from the step itself. In your case, you're using the same method to provide the title, from two sources. The problem is that we have no way of distinguishing for a given step when the source is the step and when the source is the table. The workaround is to provide another annotated method as the hook for the either the named parameter or the parsed parameter. That's not necessarily a bad practice. Adding an annotated method that calls the previous one does not duplicate functionality, simply adds another DSL step definition. At the moment, I can't think of a configurable way to distinguish between these two cases. Effectively, the parametrised scenario steps were designed to be thought as a self-contained unit and not mixed-n-match with parametrised steps. If you can think of a better way, feel free to chip in ideas.

This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira

--------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email