The documentation lacks Gherkin compatibility status

[benoitbryon]

Hello,

Is "Gherkin compatibility" a feature of lettuce?

I discovered lettuce via cucumber's wiki. I am wondering if lettuce fully supports the cucumber's Gherkin language. I mean, if I follow cucumber's wiki about writing specifications, will lettuce understand it? Yet another way to say it: if I already have specifications written for cucumber, can I switch to lettuce? Is syntax/grammar quite the same or exactly the same?

"Exactly the same" would be great because then:

• one could write specifications in a programming-language-independent way.
• you do Ruby, use Cucumber ; you do Python, use Lettuce ; the way you write specifications doesn't change.
• it may be possible to share the Gherkin part of the documentation (but this would be discussed in another ticket).

I couldn't find this information in the documentation. I searched "Gherkin" in the mailing lists too.

I am open to propose some changes in the documentation if it helps. But right now, I don't know whether to say Gherkin compatibility a feature of lettuce or not.

[vlasovskikh]

+1

[gabrielfalcao]

@benoitbryon indeed man.

[ajdavis]

I arrived here wondering the same thing as @benoitbryon.

[jfields]

+1. I'll probably try behave first, because it's clear from the docs that it reads standard gherkin.

[lucasvickers]

I'm a little confused. I see the online and locally generated documents but I see no explanation regarding full or subset gherkin support. Can anyone point me in the right direction? thanks