You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 28, 2019. It is now read-only.
When using the json formatter with a regular scenario, the json formatter records each step of the scenario and the results of each step. This is great for reports and tracking this data historically.
When using the json formatter with a scenario outline, the json formatter records the steps that make up the scenario, but only shows their results once. It then has an array of all the examples used (inferring to the user that these steps were executed N times). Would it make sense to modify the json formatter to instead dump out the steps results for each example? Treat each example as a new scenario object. That way you could track duration/status for each example you are using in the outline. It would also allow reports to inform the user which specific example and step failed and why. Yes, the json output would be a lot larger but wouldn't the added information be beneficial to most users?
The text was updated successfully, but these errors were encountered:
so it looks like when I use the --expand call I get what I want for scenario outline examples being run as individual scenarios, but when I add --format json --o cucumber.json the --expand option is ignored
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When using the json formatter with a regular scenario, the json formatter records each step of the scenario and the results of each step. This is great for reports and tracking this data historically.
When using the json formatter with a scenario outline, the json formatter records the steps that make up the scenario, but only shows their results once. It then has an array of all the examples used (inferring to the user that these steps were executed N times). Would it make sense to modify the json formatter to instead dump out the steps results for each example? Treat each example as a new scenario object. That way you could track duration/status for each example you are using in the outline. It would also allow reports to inform the user which specific example and step failed and why. Yes, the json output would be a lot larger but wouldn't the added information be beneficial to most users?
The text was updated successfully, but these errors were encountered: