Elizabeth Keogh wrote:
On Wed, Sep 2, 2009 at 12:49 AM, aslak hellesoy<[email protected]> wrote:
Hi!
I have rounded up some fine folks who are working on a new, fast parser
(based on Ragel) for Gherkin - the language that Cucumber supports.
Since Gherkin is a superset of what JBehave supports, this might be
something you would like to use - for a couple of reasons:
Hi Aslak,
Do you have any documentation for Gherkin around at all? Maybe some
examples of scenarios that differ from JBehave's? (I know you've got
Background, which makes me quite jealous already!)
Also, is there any way to get Gherkin to parse a simple G/W/T scenario
without all the "Scenario: <Whatever>" and narrative that comes before
it? JBehave does this and it makes knocking up new Scenarios very
quick; for that reason, and for backwards compatibility, I'd be keen
to keep it.
Even if we don't use your parser, I'd like for us to be working off
the same language base (hence documentation for Gherkin's supported
features would be good!). Cucumber's been an inspiration for JBehave
2; if we can keep them aligned it will be good for both teams.
I second that!
Also, while implementing the template scenario with examples (what
Cucumber calls scenario outline), we found that having a separate
keyword was unnecessary. The presence of examples was enough to imply
that it was a template/outline. Do you need to distinguish between
Scenario: and Scenario Outline: ?
Cheers
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
