Skip to content
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

Open
patoi opened this issue Sep 29, 2014 · 6 comments
Open

Upgrade Cucumber from 0.3.3 to 0.4.4 #268

patoi opened this issue Sep 29, 2014 · 6 comments

Comments

@patoi
Copy link

patoi commented Sep 29, 2014

It is working with Cucumber 0.4.4: npm install cucumber, but it throws an exception with

"format": "pioneerformat.js"

If I change this one to

"format": "pretty"

than it works fine.

@samccone
Copy link
Contributor

@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?

@sullenboom
Copy link

@samccone :
Thanks for the information. I had the same question.

You ask about a needed feature. We need for our tests "scenario outline" from cucumber v.4+.
When do you think it is implemented at pioneer?

@aindlq
Copy link

aindlq commented Feb 19, 2015

Any news on this issue, "scenario outline" could be really useful. But new cucumber is required for this feature.

@aindlq
Copy link

aindlq commented Mar 29, 2015

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

@samccone
Copy link
Contributor

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?

@aindlq
Copy link

aindlq commented Mar 31, 2015

@samccone I can do that. Should we wait for cucumber/cucumber-js#309 to land, to get rid off cucumberjs fork?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants