forked from Klaveness-Digital/cypress-cucumber-preprocessor
-
-
Notifications
You must be signed in to change notification settings - Fork 149
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
Scenario outline is not recognised in report #966
Comments
This is an issue with the json-formatter and has been reported here: cucumber/json-formatter#25 |
badeball
added a commit
that referenced
this issue
Mar 19, 2023
badeball
added a commit
that referenced
this issue
Mar 19, 2023
badeball
added a commit
that referenced
this issue
Mar 26, 2023
badeball
added a commit
that referenced
this issue
Mar 26, 2023
badeball
added a commit
that referenced
this issue
Mar 26, 2023
badeball
added a commit
that referenced
this issue
Mar 26, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Current behavior
When we use examples in scenario outline itself, the report generated is not able to decode the examples in scenario outline.
Report Output:
cuucmber-report.json:
Desired behavior
The report should have the example value itself in the scenario outline section.
Test code to reproduce
WasiqB/multiple-cucumber-html-reporter#69
Versions
Checklist
[email protected]
(package name has changed and it is no longer the most recent version, see #689).The text was updated successfully, but these errors were encountered: