On June 25, 2011, Cosimo Streppone wrote: > On Fri, 24 Jun 2011 20:18:44 +0200, Khai Do <khai...@impinj.com> wrote: > > The TAP::Formatter::JUnit formatter isn't creating 100% compatible junit > > reports. The problem is that the generated reports contain a root level > > 'testsuites' element which isn't the same as an individual junit report. > > Junit reports from junit framework only contain 'testsuite' elements. > > I use TAP::Harness::JUnit, > > http://my.opera.com/cstrep/blog/2011/03/08/continuous-integration-of-perl- > based-projects-in-hudson-jenkins > > but AFAIK that one also builds an XML file with <testsuites> as root > element.
Yes, both TAP::Harness::JUnit and TAP::Formatter::JUnit generate output with a <testsuites> root element, as they're both designed to generate output suitable for feeding into a "Hudson/Jenkins" Continuous Integration instance. Khai, if you specifically need results _without_ that element, could you not post-process the output to remove it? Further, what are you trying to feed the JUnit results into? -- Graham TerMarsch
