We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
match
There's a difference in outputted JSON from cucumber-js compared to its messages piped through cucumber-json-formatter.
cucumber-js
cucumber-json-formatter
The JSON output of cucumber-js in case of an undefined step is as following.
[ { "description": "", "elements": [ { "description": "", "id": "a-feature;a-scenario", "keyword": "Scenario", "line": 2, "name": "a scenario", "steps": [ { "arguments": [], "keyword": "Given ", "line": 3, "name": "a missing definition", "result": { "status": "undefined", "duration": 0 } } ], "tags": [], "type": "scenario" } ], "id": "a-feature", "line": 1, "keyword": "Feature", "name": "a feature", "tags": [], "uri": "features/foo.feature" } ]
However, when piping the messages output through cucumber-json-formatter I get the following.
[ { "description": "", "elements": [ { "description": "", "id": "a-feature;a-scenario", "keyword": "Scenario", "line": 2, "name": "a scenario", "steps": [ { "keyword": "Given ", "line": 3, "name": "a missing definition", "result": { "status": "undefined" }, "match": { "location": "features/foo.feature:3" } } ], "type": "scenario" } ], "id": "a-feature", "keyword": "Feature", "line": 1, "name": "a feature", "uri": "features/foo.feature" } ]
Notice the diff (using json-diff).
[ { - tags: [ - ] elements: [ { - tags: [ - ] steps: [ { - arguments: [ - ] + match: { + location: "features/foo.feature:3" + } result: { - duration: 0 } } ] } ] } ]
Steps to reproduce the behavior:
git clone https://github.com/badeball/reproducible-issues.git
cd reproducible-issues/cucumber/undefined-step
npx @cucumber/cucumber
npx json-diff report.json <(cat report.ndjson | cucumber-json-formatter)
The samme problem exist for ambiguous steps as well. The same steps can be run, just in the ambiguous-step of the above-mentioned repository.
ambiguous-step
The text was updated successfully, but these errors were encountered:
No branches or pull requests
π What did you see?
There's a difference in outputted JSON from
cucumber-js
compared to its messages piped throughcucumber-json-formatter
.β What did you expect to see?
The JSON output of
cucumber-js
in case of an undefined step is as following.However, when piping the messages output through
cucumber-json-formatter
I get the following.Notice the diff (using json-diff).
π¦ 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/undefined-step
npx @cucumber/cucumber
npx json-diff report.json <(cat report.ndjson | cucumber-json-formatter)
π Any additional context?
The samme problem exist for ambiguous steps as well. The same steps can be run, just in the
ambiguous-step
of the above-mentioned repository.The text was updated successfully, but these errors were encountered: