Skip to content
New issue

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

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

JUnit XML Reporting #63

Closed
jbpros opened this issue May 11, 2012 · 4 comments
Closed

JUnit XML Reporting #63

jbpros opened this issue May 11, 2012 · 4 comments

Comments

@jbpros
Copy link
Member

jbpros commented May 11, 2012

Originally filed on cucumber-tck as #14 by @s9tpepper.
@aslakhellesoy aslakhellesoy mentioned this issue May 17, 2012
Closed
jbpros added a commit that referenced this issue Jun 17, 2012
@jbpros
Refactor listener infrastructure (#35, #59, #63)
837c021 
* 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 added a commit that referenced this issue Jun 19, 2012
@jbpros
Extract summary logger from progress formatter (#59, #63)
3057098 
Feature run summaries can now be reused among formatters.
jbpros added a commit that referenced this issue Jun 20, 2012
@jbpros
Extract common formatter methods (#59, #63)
5b45be4
@afternoon
Copy link

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

<?xml version="1.0" encoding="UTF-8" ?>
<testsuites>
<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>
</testsuite>
</testsuites>

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.

@afternoon
Copy link

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

@jbpros jbpros removed this from the ancillary features milestone Oct 10, 2015
@charlierudolph
Copy link
Member

Closing in favor of #516

@lock
Copy link

lock bot commented Oct 25, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Oct 25, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@afternoon @jbpros @charlierudolph