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
This project was setup to facilitate a migration away from the JSON report format so it could be deprecated gracefully. Unfortunately the JSON report is more entrenched than expected. As such the core team rolled back the decision to deprecate it.
As a result -because each Cucumber implementation can generate JSON reports- from the perspective of the Cucumber core team there is little to no reason to maintain this tool at this point in time.
However:
Cypress Cucumber Preprocessor users do depends on this tool.
For the first part we are looking for maintainers.
Some reasons to step forward:
Be a part of a welcoming community of developers who take test-driven development for granted. ππ
Know that the Cucumber community has an explicit commitment to diversity, equity and inclusion and that if you're from an under-represented minority in tech, you'll be welcome here. βπΏπ³οΈβπβ€οΈ
All of these are helpful and very much appreciated.
We have limited Go fluency in the team of regular maintainers at the moment, but we're here to help and available to pair with you if you need help figuring something out.
If you're willing to help, please let us know in the comments, or come for a chat in the Community Slack in the #commiters channel.
The text was updated successfully, but these errors were encountered:
As of March 26, the aboe-mentioned badeball/cypress-cucumber-preprocessor#870 was completed. The preprocessor now natively generates messages and uses the exported member JsonFormatter of the NPM module @cucumber/cucumber to generate JSON reports.
This project was setup to facilitate a migration away from the JSON report format so it could be deprecated gracefully. Unfortunately the JSON report is more entrenched than expected. As such the core team rolled back the decision to deprecate it.
As a result -because each Cucumber implementation can generate JSON reports- from the perspective of the Cucumber core team there is little to no reason to maintain this tool at this point in time.
However:
So the way forward would consist of two phases:
Maintain the tool as is.
Implement the reporting tool natively in other languages following the pattern used by the html-formatter project. This could potentially be combined with Native JSON formatterΒ badeball/cypress-cucumber-preprocessor#870.
For the first part we are looking for maintainers.
Some reasons to step forward:
Here are some ways you can help the project:
All of these are helpful and very much appreciated.
We have limited Go fluency in the team of regular maintainers at the moment, but we're here to help and available to pair with you if you need help figuring something out.
If you're willing to help, please let us know in the comments, or come for a chat in the Community Slack in the #commiters channel.
The text was updated successfully, but these errors were encountered: