Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

The documentation lacks Gherkin compatibility status #188

Open
benoitbryon opened this Issue Oct 18, 2011 · 5 comments

Comments

Projects
None yet
6 participants
Contributor

benoitbryon commented Oct 18, 2011

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.

Owner

gabrielfalcao commented Oct 19, 2011

@benoitbryon indeed man.

ajdavis commented Nov 14, 2011

I arrived here wondering the same thing as @benoitbryon.

jfields commented Dec 21, 2011

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

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

@ches ches referenced this issue in ensime/ensime-vim Jun 9, 2016

Merged

Introduce lettuce tests #248

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment