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
The JSON formatter is implemented in cucumber.js, cucumber-ruby and cucumber-jvm. It's become the defacto standard for machine-readable output from Cucumber, but it has several flaws:
There is no schema for the output, so different platforms implement it inconsistently, causing problems for consumers
It sometimes causes out of memory problems for large suites
It does a poor job at representing results for background and scenario outlines
Results cannot be consumed until Cucumber has finished
We should deprecate this in version 7 and encourage users and tool vendors to migrate to a new protobuf formatter outputting cucumber-messages.
The protobuf formatter addresses all of the problems with the json formatter:
Uh oh!
There was an error while loading. Please reload this page.
The JSON formatter is implemented in cucumber.js, cucumber-ruby and cucumber-jvm. It's become the defacto standard for machine-readable output from Cucumber, but it has several flaws:
We should deprecate this in version 7 and encourage users and tool vendors to migrate to a new
protobuf
formatter outputting cucumber-messages.The
protobuf
formatter addresses all of the problems with thejson
formatter:See a89eae3 for more details.
The text was updated successfully, but these errors were encountered: