Need to generate XML report in JUnit's format about googletest HOT 15 CLOSED

Sad that after all this time, Google Test's output still isn't entirely compatible with JUnit.

from googletest.

Any news on junit_xml support?

from googletest.

Still not available; --gtest_output=xml still produce incompatible output. This is required for Jenkins, SonarQube like external analyzers.

mytest --gtest_output=junit_xml:output.xml
WARNING: unrecognized output format "junit_xml" ignored.

from googletest.

I also need a xml format compatible to SonarQube report.
Does anyone have any news?

from googletest.

Is it available in latest release of gtest.

Original comment by [email protected] on 25 Aug 2009 at 11:29

from googletest.

I guess google doesn't use GitLab CI and SonarQube. So it won't output it ... unless any of you implemented it.

from googletest.

I'd like to request a higher priority on this issue.  We (and many others) are 
using
Continuous Integration systems that all have mechanisms for parsing JUnit and 
in some
cases CppUnit XML results.  Right now, Google Test is not an alternative for 
these
people because of the lack of reporting in a standard way.

Original comment by [email protected] on 16 Sep 2008 at 5:01

from googletest.

Changed to high priority.

Original comment by [email protected] on 17 Sep 2008 at 6:55

• Added labels: Priority-High
• Removed labels: Priority-Low

from googletest.

[email protected] reported:

<quote>
I've tried gtest with Cruise Control and seems xml output of gtest is
a bit different than CC expects.

CC expects this format:
<testsuite name="AllTests" ...>
 <testsuite name="test_case_name" ...>
   <testcase name="test_name" ...>
     <failure ...>Error message</failure>
   </testcase>
 </testsuite>
</testsuite>

But gtest uses this:
<testsuite name="AllTests" ...>
 <testsuite name="test_case_name" ...>
   <testcase name="test_name" ...>
     <failure message="Error message"/>
   </testcase>
 </testsuite>
</testsuite>

The difference is the placement of the "message". Because of this
difference CC can't display the error message.
You have to know, CC works very well with JUnit, so seems junit xml
output and gtest xml output is a bit different..
</quote>

Also, I heard report that in JUnit's output the time unit is second (e.g. 2.3), 
while 
Google Test uses millisecond (e.g. 2300).

Original comment by [email protected] on 19 Sep 2008 at 5:56

from googletest.

Google Test's XML output format has been changed to match JUnit/Ant's in the 
trunk.

Original comment by [email protected] on 26 Sep 2008 at 4:12

• Changed state: Fixed

from googletest.

Jenkins xUnit support it https://wiki.jenkins-ci.org/display/JENKINS/xUnit+Plugin

from googletest.

But not everyone can use this plugin, unfortunately.
So this is quite bad...

from googletest.

FYI, Jenkins has xunit plugin that converts googletest xml to junit format: https://plugins.jenkins.io/xunit/.

from googletest.

Thanks, though I don't think it is very suitable for GitLab CI since it is written in Java and requires its runtime. For pipelines already using both Google Test and JVM it may be feasible to adopt it. But for another ones ... I don't think it worths.

from googletest.

Is there still no update on this??? Is Google Test still not producing JUnit XML output?

from googletest.