[Zope-dev] Should we merge collective.xmltestreport into zope.testrunner?

[Hanno Schlichting]

On Sun, Jul 25, 2010 at 5:36 AM, Martin Aspeli <optilude+lists at gmail.com> wrote:
> A while back, I wrote collective.xmltestreport [1,2]. In short, it's a
> wrapper around zope.testing's test runner that can produce output in
> an XML format compatible with the xUnit family of testing tools. This
> is useful for integrating with things like Hudson, which can parse
> these kinds of files.
>
> The problem is that changes in zope.testing/zope.testrunner keep
> breaking collective.xmltestreport. At first, I was using "-x" as the
> option to turn on XML output, before zope.testing took that option as
> its own. Now, with version 3.10, it's broken again, because it's
> trying to import zope.testing.testrunner, which is no longer there.
>
> I wonder if it'd be a good idea to just merge this functionality into
> zope.testrunner itself?

We recently merged in support for subunit [0], which claims to have
amongst others "subunit2junitxml - convert a subunit stream to a JUnit
XML representation.".

That sounds to me very much like the same functionality. Having two
ways of getting the same result seems suboptimal to me. But I haven't
looked into subunit yet, so I'm not sure if it is cross-platform and
easily installable. I'd love to see someone write up some
documentation on how to use it inside Hudson ;)

Hanno

[0] https://launchpad.net/subunit/