On 25 July 2010 16:58, Hanno Schlichting <ha...@hannosch.eu> wrote:
> On Sun, Jul 25, 2010 at 5:36 AM, Martin Aspeli <optilude+li...@gmail.com>
>> 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 , 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 ;)
Definitely. collective.xmltestreport is a bit clunky anyway. If we
have something better, I'm all for it.
>  https://launchpad.net/subunit/
Are there any docs on how this actually works? I see a changelog entry
for zope.testing, but no information on how to actually use it. :(
Zope-Dev maillist - Zope-Dev@zope.org
** No cross posts or HTML encoding! **
(Related lists -