| Issue 30: | Need to generate XML report in JUnit's format | |
| 5 people starred this issue and may be notified of changes. | Back to list |
Google Test's XML report format differs from JUnit's slightly. While we cannot change it without breaking some existing processes, a quick short-term solution is to write an XSLT to convert Google Test's output to JUnit's format (it's also very flexible in case JUnit changes its format). In the long run, we could extend the --gtest_output flag with an option to use the JUnit format, e.g. --gtest_output=junit_xml instead of --gtest_output=xml This will be more work to implement but is easier for the users.
Sep 16, 2008
#1
bill.wa...@gmail.com
Sep 17, 2008
Changed to high priority.
Labels:
-Priority-Low Priority-High
Sep 18, 2008
balazs.dan@gmail.com 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).
Sep 26, 2008
Google Test's XML output format has been changed to match JUnit/Ant's in the trunk.
Status:
Fixed
Aug 25, 2009
Is it available in latest release of gtest. |
|
| ► Sign in to add a comment |