-
-
Notifications
You must be signed in to change notification settings - Fork 6
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
Inaccurate output of scenario outlined with parameterized name #25
Comments
Hi -- Would like to know if this issue will be fixed in next release ? ... We are using this json for Rally test case generation, test result update |
Cucumber is an open source project and mostly runs on volunteers. Now it appears that nobody has been interested yet in providing a solution. Unless you are interested in providing this solution it is unlikely to happen at all. Though you may also want to consider upgrading your tooling to use the |
@mpkorstanje - Is it possible if you can elaborate more on - upgrading your tooling to use the ndjson output from the message formatter directly instead. Still facing this isse and tried multiple ways but not able to resolve it. |
π What did you see?
There's a difference in outputted JSON from
cucumber-js
compared to its messages piped throughcucumber-json-formatter
when the scenario outline contains a parameter.β What did you expect to see?
The JSON output of
cucumber-js
in case of such scenario.However, when piping the messages output through
cucumber-json-formatter
I get the following.Notice the diff (using json-diff), IE. the parameter in the
name
property has not been replaced with the value.π¦ Which tool/library version are you using?
π¬ How could we reproduce it?
Steps to reproduce the behavior:
git clone https://github.com/badeball/reproducible-issues.git
cd reproducible-issues/cucumber/outline-name-parameter
npx @cucumber/cucumber
npx json-diff report.json <(cat report.ndjson | cucumber-json-formatter)
The text was updated successfully, but these errors were encountered: