Cuke4Duke migration docs #239
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
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. |
|
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 this...so many different languages & configurations! |
aslakhellesoy
added a commit
that referenced
this pull request
Mar 26, 2012
Cuke4Duke migration docs
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.