I debugged it and as it seems, this method does not work as I would expect
it: org.jbehave.core.steps.StepCreator.ParameterisedStep.parametriseStep()
The org.jbehave.core.annotations.Named annotation supports only one
value. But in my use cases I need two values: creditAccount and
debitAccount.
As it seems it can be solved with configuring the MostUsefuleConfiguration
like this:
.useParameterControls(new
ParameterControls().useDelimiterNamedParameters(true))
It is even documented here:
http://jbehave.org/reference/stable/parametrised-scenarios.html(Parametrisation
by name delimiters).
Hi,
this is indeed one of the solutions.
I agree that it would be more useful as a default. Please raise a JIRA issue
for this and we'll add it to next release.
Cheers
On 7 Feb 2014, at 15:23, Hans Schwäbli bugs.need.love@gmail.com wrote:
As it seems it can be solved with configuring
I have two steps like this with a examples table where the values are
defined:
Given the account data of debitAccount is known
Given the account data of creditAccount is known
First I tried this in the step class method for the two steps above:
@Given(the account data of $debitAccount is known)
Hi
what is the stated intention here? You want two steps to match the
same method with different parameter names?
Can you please provide a sample project - inclusive of textual stories
and steps class that reproduces your issue?
Thanks
On 06/02/2014 16:52, Hans Schwäbli wrote:
I have
