Cuke4Duke migration docs #239

merged 1 commit into from Mar 26, 2012


None yet

3 participants

jharmn commented Mar 2, 2012

Perhaps there's a better place to host this, but at the moment the README seems to be the general starting point for RTFM. I know it took me a lot of combing through the Cukes Google group to figure out how to configure things to run the way our team wanted, so I thought I'd pass it along.
The only missing piece is how to have Java included, thus producing JUnit reports. I have this configuration as well, but it didn't seem to exactly fit in with the matra of 'migration', seeing that everyone coming over from Cuke4Duke will have pure Groovy code run via JRuby.

Hope it helps!

P.S. Keep up the great work, we're loving the pure JVM implementation SOOO much better.

dkowis commented Mar 2, 2012

Thanks for making this! I'd mention that this is a migration from Cuke4Duke to Cucumber-jvm Groovy Backend, however, since it is specific to that.

For example: In my case, we didn't have any groovy code run at all, but a lot of Jruby, and some Spring based steps.

jharmn commented Mar 2, 2012

Point taken; I definitely have a groovy-centric view of things, in this case. I guess it's probably tough for the Cuke folks to consider all of the different viewpoints out there on how to use many different languages & configurations!

@aslakhellesoy aslakhellesoy merged commit 6005d6c into cucumber:master Mar 26, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment