Closed davidjgoss closed 2 weeks ago
This PR replaces the existing JUnit formatter - built using the old-style pattern - with the one from https://github.com/cucumber/junit-xml-formatter.
The new formatter has parity with the Java implementation and uses the new plugin-based pattern with messages and query.
(This is not a breaking change because the old formatter was never publicly exported.)
This text was originally generated from a template, then edited by hand. You can modify the template here.
coverage: 97.765% (-0.07%) from 97.838% when pulling 0cc5c7b91af93c9d25f1163482af12bf1dba8bb0 on junit-formatter-messages into ddf424a7a55e45535a2f2c5f8b04562ed7a0c5fc on main.
🤔 What's changed?
This PR replaces the existing JUnit formatter - built using the old-style pattern - with the one from https://github.com/cucumber/junit-xml-formatter.
⚡️ What's your motivation?
The new formatter has parity with the Java implementation and uses the new plugin-based pattern with messages and query.
🏷️ What kind of change is this?
(This is not a breaking change because the old formatter was never publicly exported.)
📋 Checklist:
This text was originally generated from a template, then edited by hand. You can modify the template here.