Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

JUnit XML Reporting #63

jbpros opened this Issue May 11, 2012 · 3 comments


None yet
3 participants

jbpros commented May 11, 2012

Originally filed on cucumber-tck as #14 by @s9tpepper.

@aslakhellesoy aslakhellesoy referenced this issue in cucumber/cucumber-jvm May 17, 2012


Surefire-report incompatible with Sonar #322

@jbpros jbpros added a commit that referenced this issue Jun 17, 2012

@jbpros jbpros Refactor listener infrastructure (#35, #59, #63)
* Extract common listener behaviour from progress formatter
* Extract stats journal from progress formatter

Theses changes will ease the implementation of new listeners (e.g. the pretty, JSON and jUnit formatters).

@jbpros jbpros added a commit that referenced this issue Jun 19, 2012

@jbpros jbpros Extract summary logger from progress formatter (#59, #63)
Feature run summaries can now be reused among formatters.

The JUnit XML format is pretty simple, e.g.

<?xml version="1.0" encoding="UTF-8" ?>
<testsuite name="XXX" errors="0" tests="1" failures="0" time="1.986" timestamp="2014-08-22T16:57:55">
  <testcase classname="XXX" name="YYY" time="1.986"></testcase>

Looking at the code, producing a JUnit formatter should be a case of handling the after feature and after scenario events to map those structures to testsuite and testcase elements.

I didn't do much digging, but I wasn't sure what data would be passed to those events. If anyone has any hints on where I should look, that would be great.

This issue should probably be closed as a duplicate of #100.

@jbpros jbpros removed this from the ancillary features milestone Oct 10, 2015


charlierudolph commented Aug 29, 2016

Closing in favor of #516

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment