Hi Christopher,
yes, that is the intended scope of Scenario Examples.
But you can also use the ExamplesTable to parse your tabular input for
internal implementation in a step method.
@When("I do something with a table $tableContent")
public void doSomethingWithATable(String tableContent){
ExamplesTable table = new ExamplesTable(tableContent);
// use table to retrieve contents by row
}
The difference here is that you can use the entire table content in the
same scenario step, and not one line per scenario execution as when
using the Examples: keyword.
I've been meaning to had this use case to the docs, just have not got
around to it. In one of my current projects, we've found it quite
useful in cutting down files and making scenarios more expressive.
NOTE: if you are using Windows, you may still be bitten by the regex
issue for long table with repeated values, especially at start of the
the lines. Workaround, is to put the columns with most varying values
as much to the left as possible.
Cheers
Christopher Gardner wrote:
It looks like just using the Examples approach should suffice.
On Tue, Nov 24, 2009 at 8:05 AM, Christopher Gardner
<[email protected]> wrote:
Is there a way to get the effect of cucumber's multiline step feature
in JBehave?
http://wiki.github.com/aslakhellesoy/cucumber/multiline-step-arguments
This would be useful to set up data to test search functionality
without having to resort to an external file.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
