-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Confusing error message from json formatter #197
Comments
Do you get the same error with the latest versions of cucumber (1.1.3) ? |
Yes
|
I do too on 1.2.1. /Users/jwillson/.rvm/gems/ruby-1.9.2-p320/bin/ruby_noexec_wrapper:14:in eval' /Users/jwillson/.rvm/gems/ruby-1.9.2-p320/bin/ruby_noexec_wrapper:14:in '
|
+1 c:\test\auto>cucumber --format json_pretty --out reports/reports.json |
@fuzzyweapon @wilken could you show us the feature file (or ideally pare it down to a representative test case) that causes this? |
Hi, this feature file causes the error:
|
Thanks Morten. Are any of these steps failing, or undefined? |
No everything is fine and i can produce the report in html and json. only json_pretty fails
|
It looks like the problem is that JsonPretty is outdated :( @mattwynne what do you think about this approach? |
@os97673 sounds reasonable. Can you show me the code? |
@mattwynne I've created cucumber/gherkin#243 with gherkin's changes.
|
For now JsonPretty is an empty subclass of Json. It doesn't produce prettyfied json, but at least id doesn't throws exceptions
While we are discussing changes for Gherkin, I've pushed simple fix which make JsonPretty an empty subclass of Json. This way it at least doesn't throw exceptions ;) |
In cucumber/gherkin#243 we decided to change |
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. |
$ cucumber -t @step_matcher -f json_pretty
Feature file being parsed is https://github.com/flashquartermaster/Cuke4AS3/blob/master/Cuke4AS3/test/features/cuke4as3/step-matcher.feature
The text was updated successfully, but these errors were encountered: