Problem with JUnit Publishing

Benny Higdon

(16●1●1) Feb 12 '10, 5:30 p.m.

Hi! We're using RTC to automate WebSphere Integration Developer (WID) 6.2.0.2 component test. WID is an IBM integrated development environment. Its component test allows you to define test suites and test cases for automated testing of the integration components.

Our test runs fine but there's an error parsing the XML file when publishing the JUnit results.

The output from the WID component test looks like the following:


    &lt;xml&gt;

    &lt;resource&gt;

       &lt;testsuite&gt;

          &lt;testcase&gt;

             &lt;variation&gt;

                &lt;severity&gt;pass&lt;/severity&gt;

                &lt;description&gt;Default pass&lt;/description&gt;

                &lt;resource&gt;HelloWorldComponentTest&lt;/resource&gt;

             &lt;/variation&gt;

          &lt;/testcase&gt;

       &lt;/testsuite&gt;

       &lt;testsuite&gt;

          &lt;testcase&gt;

             &lt;variation&gt;

                &lt;severity&gt;pass&lt;/severity&gt;

                &lt;description&gt;Default pass&lt;/description&gt;

                &lt;resource&gt;HelloWorldComponentTest&lt;/resource&gt;

             &lt;/variation&gt;

          &lt;/testcase&gt;

       &lt;/testsuite&gt;

    &lt;/resource&gt;

The warning message is for the "resource" tag. I'm not sure if it's for the high-level one or the one in the variations.

Is this a valid JUnit XML file? Should the RTC publish be able to handle this? We have an old version of RTC (1.0.1.1) so it's possible this is fixed in a more recent version.

FWIW, I've tried searching for a schema or DTD that defines the JUnit test results but I couldn't find anything.

Thanks in advance for any help.

Benny L. Higdon

0 votes

8 answers

9,563 views

0 votes

8 answers

Permanent link

Benny Higdon

(16●1●1) Feb 19 '10, 10:47 p.m.

Hi! We're using RTC to automate WebSphere Integration Developer (WID) 6.2.0.2 component test. WID is an IBM integrated development environment. Its component test allows you to define test suites and test cases for automated testing of the integration components.

Our test runs fine but there's an error parsing the XML file when publishing the JUnit results.

The output from the WID component test looks like the following:
    &lt;xml&gt;

    &lt;resource&gt;

       &lt;testsuite&gt;

          &lt;testcase&gt;

             &lt;variation&gt;

                &lt;severity&gt;pass&lt;/severity&gt;

                &lt;description&gt;Default pass&lt;/description&gt;

                &lt;resource&gt;HelloWorldComponentTest&lt;/resource&gt;

             &lt;/variation&gt;

          &lt;/testcase&gt;

       &lt;/testsuite&gt;

       &lt;testsuite&gt;

          &lt;testcase&gt;

             &lt;variation&gt;

                &lt;severity&gt;pass&lt;/severity&gt;

                &lt;description&gt;Default pass&lt;/description&gt;

                &lt;resource&gt;HelloWorldComponentTest&lt;/resource&gt;

             &lt;/variation&gt;

          &lt;/testcase&gt;

       &lt;/testsuite&gt;

    &lt;/resource&gt;
The warning message is for the "resource" tag. I'm not sure if it's for the high-level one or the one in the variations.

Is this a valid JUnit XML file? Should the RTC publish be able to handle this? We have an old version of RTC (1.0.1.1) so it's possible this is fixed in a more recent version.

FWIW, I've tried searching for a schema or DTD that defines the JUnit test results but I couldn't find anything.

Thanks in advance for any help.

Benny L. Higdon

I've verified that IBM is using an internal format. Also, the latest WID release (V7) also uses this proprietary format :-(

By trial and error, I was able to create an XSLT to generate a JUnit compatible format. So, I'm good to go.

Benny L. Higdon

0 votes

Permanent link

Nick Edgar

JAZZ DEVELOPER (6.5k●7●11) Apr 18 '10, 2:40 p.m.

Hi Benny,

I see this was never responded to. Sorry about that. Is this still an issue for you?
Regarding the non-standard format, are you saying that WID outputs a non-standard format, or that RTC does not honour the standard format, or both?
Even if it's non-standard, we could perhaps enhance the existing JUnit publisher to understand this format, if it makes sense.

Thanks,
Nick

0 votes

Permanent link

Benny Higdon

(16●1●1) Apr 19 '10, 11:13 a.m.

Nick,

This is no longer an issue since I was able to create a stylesheet to transform the WID format into one that RTC would publish.

I believe that it is WID that is using a non-standard format. However, I'm not a JUnit guru so I can't say for sure. I included an example of the WID output in my append so perhaps someone more knowledgeable about JUnit can comment.

As for existing the existing JUnit publisher, I'm not sure that it should be tied to an IBM proprietary format.

Benny

0 votes

Permanent link

Nick Edgar

JAZZ DEVELOPER (6.5k●7●11) Apr 19 '10, 11:44 a.m.

Looking at the source for Ant's XMLJUnitResultFormatter, it only uses <testsuite> as the root element(s) and knows nothing about <resource> elements, so I agree the WID format is non-standard. And I agree that it would be odd for RTC to support this. Thanks for clarifying.

0 votes

Permanent link

Chris Novak

(26●2●1) Nov 23 '10, 10:55 p.m.

Is anyone aware of an Ant task than can be used to parse a WID component test output XML file and publish the results to the RTC server as a part of the build report?

0 votes

Permanent link

Nick Edgar

JAZZ DEVELOPER (6.5k●7●11) Nov 24 '10, 10:24 a.m.

Since the format is so close (yet so far) from the JUnit XML file format, it should be pretty straightforward to come up with a sed or awk shell script, or XSLT transform, that removes the extra <resource> tags.

You could then use the existing junitLogPublisher task.

0 votes

Permanent link

Nick Edgar

JAZZ DEVELOPER (6.5k●7●11) Nov 24 '10, 1:37 p.m.

For an example of using XSLT to process test results, see:
http://jazz.net/forums/viewtopic.php?t=5906

0 votes

Permanent link

Nick Edgar

JAZZ DEVELOPER (6.5k●7●11) Nov 25 '10, 12:04 p.m.

Benny actually posted an XSLT to do exactly as suggested above:
http://ibmforums.ibm.com/forums/message.jspa?messageID=1762894

Not sure if that's behind the firewall, so I'm posting it here too:

&lt;?xml version=&quot;1.0&quot;?&gt;



&lt;xsl&#58;stylesheet xmlns&#58;xsl=&quot;http&#58;//www.w3.org/1999/XSL/Transform&quot; version=&quot;1.0&quot;&gt;



    &lt;xsl&#58;template match=&quot;@*|node&#40;&#41;&quot;&gt;

        &lt;xsl&#58;copy&gt;

            &lt;xsl&#58;apply-templates select=&quot;@*|node&#40;&#41;&quot;/&gt;

        &lt;/xsl&#58;copy&gt;

    &lt;/xsl&#58;template&gt;



    &lt;xsl&#58;template match=&quot;resource&quot;&gt;



        &lt;xsl&#58;element name=&quot;testsuites&quot;&gt;

            &lt;xsl&#58;apply-templates select=&quot;node&#40;&#41;&quot;/&gt;

        &lt;/xsl&#58;element&gt;

    &lt;/xsl&#58;template&gt;



    &lt;xsl&#58;template match=&quot;testcase/variation&quot;/&gt;



    &lt;xsl&#58;attribute-set name=&quot;testsuiteAttrs&quot;&gt;

        &lt;xsl&#58;attribute name=&quot;errors&quot;&gt;

            &lt;xsl&#58;value-of select=&quot;@totalTests - count&#40;./testcase&#91;@result = 'pass'&#93;&#41;&quot; /&gt;



        &lt;/xsl&#58;attribute&gt;

        &lt;xsl&#58;attribute name=&quot;failures&quot;&gt;0&lt;/xsl&#58;attribute&gt;

        &lt;xsl&#58;attribute name=&quot;name&quot;&gt;&lt;xsl&#58;value-of select=&quot;@name&quot;/&gt;&lt;/xsl&#58;attribute&gt;

        &lt;xsl&#58;attribute name=&quot;tests&quot;&gt;&lt;xsl&#58;value-of select=&quot;@totalTests&quot;/&gt;&lt;/xsl&#58;attribute&gt;

        &lt;xsl&#58;attribute name=&quot;time&quot;&gt;

            &lt;xsl&#58;value-of select=&quot;&#40;@end - @start&#41; div 1000&quot;/&gt;&lt;/xsl&#58;attribute&gt;

    &lt;/xsl&#58;attribute-set&gt;



    &lt;xsl&#58;template match=&quot;testsuite&quot;&gt;



        &lt;xsl&#58;element name=&quot;testsuite&quot; use-attribute-sets=&quot;testsuiteAttrs&quot;&gt;

            &lt;xsl&#58;apply-templates/&gt;

        &lt;/xsl&#58;element&gt;

    &lt;/xsl&#58;template&gt;



    &lt;xsl&#58;attribute-set name=&quot;testcaseAttrs&quot;&gt;

        &lt;xsl&#58;attribute name=&quot;classname&quot;&gt;&lt;xsl&#58;value-of select=&quot;@name&quot;/&gt;&lt;/xsl&#58;attribute&gt;

        &lt;xsl&#58;attribute name=&quot;name&quot;&gt;&lt;xsl&#58;value-of select=&quot;@name&quot;/&gt;&lt;/xsl&#58;attribute&gt;

        &lt;xsl&#58;attribute name=&quot;time&quot;&gt;



            &lt;xsl&#58;value-of select=&quot;&#40;@end - @start&#41; div 1000&quot;/&gt;

        &lt;/xsl&#58;attribute&gt;

    &lt;/xsl&#58;attribute-set&gt;



    &lt;xsl&#58;template match=&quot;testcase&quot;&gt;

        &lt;xsl&#58;element name=&quot;testcase&quot; use-attribute-sets=&quot;testcaseAttrs&quot;&gt;

            &lt;xsl&#58;apply-templates/&gt;

        &lt;/xsl&#58;element&gt;

    &lt;/xsl&#58;template&gt;



	

&lt;/xsl&#58;stylesheet&gt;

Benny, if you're not OK with me posting it here, just let me know and I'll delete this post.

0 votes

Your answer

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers

Answers and Comments

Question details

rational-team-concert

× 42,912

Question asked: Feb 12 '10, 5:30 p.m.

Question was seen: 9,563 times

Last updated: Feb 12 '10, 5:30 p.m.

Problem with JUnit Publishing

8 answers

9,563 views

0 votes

8 answers

Your answer

Follow this question

Question details

Related questions