-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade Cucumber from 0.3.3 to 0.4.4 #268
Comments
@patoi we are using an older version of cucumber on purpose. Since cucumber updated their coffeescript compiler the stack traces that you get back from cucumber have become useless. We have also applied a few patches on top of cucumber to allow for custom formatters. Is there something you want from the never version of cucumber? |
@samccone : You ask about a needed feature. We need for our tests "scenario outline" from cucumber v.4+. |
Any news on this issue, "scenario outline" could be really useful. But new cucumber is required for this feature. |
fyi, I've tried pioneer with latest cucumberjs and "format": "pretty". It works great. "scenario outline" works out of the box. And as for me stack trace is not bad at all. For everyone who are using pioneer and need "scenario outline" feature from latest cucumumber, you can just use npm shrinkwrap to override cucumberjs version - https://docs.npmjs.com/cli/shrinkwrap |
hey @ArtemKozlov yeah this was using an old version because of stack traces and custom formatters, and promise returns. If you think everything is working would you like to open a PR? |
@samccone I can do that. Should we wait for cucumber/cucumber-js#309 to land, to get rid off cucumberjs fork? |
It is working with Cucumber 0.4.4: npm install cucumber, but it throws an exception with
If I change this one to
than it works fine.
The text was updated successfully, but these errors were encountered: