aslak hellesoy
2015-09-04 08:26:14 UTC
Hi Scott,
Thanks for your kind words! (I'm copying in the Cucumber mailing list since
this is of public interest)
There are many official Cucumber implementations now [1], but I suppose you
are talking about the ruby one.
I'm aware of several unofficial Cucumber implementations in Go (and also
other languages), but I'm not deeply familiar with any of them.
With the growing popularity of Cucumber, and new unofficial implementations
appearing, what we need is a specification for Cucumber.
With this I hope that the various implementations will be more uniform, and
that some of the unofficial ones can be included in the official family.
Or better yet - that someone writes one from scratch under the Cucumber
organisation.
The first step is to get the Cucumber specification to a level of quality
where it can be used as a guide to write new Cucumber implementations.
Is this something you'd be interested in helping out with? I hope to
assemble a team of 5-10 people to contribute to this spec and make it
complete enough in a couple of months time.
Cheers,
Aslak
[1] https://github.com/cucumber/cucumber#official-cucumber-implementations
Thanks for your kind words! (I'm copying in the Cucumber mailing list since
this is of public interest)
There are many official Cucumber implementations now [1], but I suppose you
are talking about the ruby one.
I'm aware of several unofficial Cucumber implementations in Go (and also
other languages), but I'm not deeply familiar with any of them.
With the growing popularity of Cucumber, and new unofficial implementations
appearing, what we need is a specification for Cucumber.
With this I hope that the various implementations will be more uniform, and
that some of the unofficial ones can be included in the official family.
Or better yet - that someone writes one from scratch under the Cucumber
organisation.
The first step is to get the Cucumber specification to a level of quality
where it can be used as a guide to write new Cucumber implementations.
Is this something you'd be interested in helping out with? I hope to
assemble a team of 5-10 people to contribute to this spec and make it
complete enough in a couple of months time.
Cheers,
Aslak
[1] https://github.com/cucumber/cucumber#official-cucumber-implementations
Hello,
Thanks for all the wonderful work on cucumber. We have built up a huge
test suite with cucumber, almost 5000 scenarios, and it's starting to run
really slow on the windows machines some of our developers are using.
It takes about 4 minutes to run all the tests on my mac, so I'm assuming
it's a ruby/windows/fileio/forking type issue that I'd rather not try and
solve.
We use the wire protocol to talk to cucumber-lua which is the environment
that all the code is actually in.
All of that context to say, I've noticed some activity on the cucumber3-go
implementation, and I was wondering if you knew of any work to run the
tests through the wire protocol in go.
That way I could get a nice statically compiled cucumber.exe that I would
expect should be much faster then the ruby/windows combination.
I've done some work in go, and could try to hack something together if I
was pointed in the right direction to get started.
Thanks for your time
Scott
Thanks for all the wonderful work on cucumber. We have built up a huge
test suite with cucumber, almost 5000 scenarios, and it's starting to run
really slow on the windows machines some of our developers are using.
It takes about 4 minutes to run all the tests on my mac, so I'm assuming
it's a ruby/windows/fileio/forking type issue that I'd rather not try and
solve.
We use the wire protocol to talk to cucumber-lua which is the environment
that all the code is actually in.
All of that context to say, I've noticed some activity on the cucumber3-go
implementation, and I was wondering if you knew of any work to run the
tests through the wire protocol in go.
That way I could get a nice statically compiled cucumber.exe that I would
expect should be much faster then the ruby/windows combination.
I've done some work in go, and could try to hack something together if I
was pointed in the right direction to get started.
Thanks for your time
Scott
--
Posting rules: http://cukes.info/posting-rules.html
---
You received this message because you are subscribed to the Google Groups "Cukes" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cukes+***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Posting rules: http://cukes.info/posting-rules.html
---
You received this message because you are subscribed to the Google Groups "Cukes" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cukes+***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.