Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Match GTest JUnit XML Format #1260

Open
Ipiano opened this issue Apr 23, 2018 · 0 comments
Open

Feature Request: Match GTest JUnit XML Format #1260

Ipiano opened this issue Apr 23, 2018 · 0 comments

Comments

@Ipiano
Copy link

Ipiano commented Apr 23, 2018

Description

I am working on a Qt + ROS 2 project and I will be using Catch as my unit testing framework. The ROS 2 build system, Ament, supports any test framework which exports JUnit XML files that follow the GTest standards described here: https://github.com/google/googletest/blob/master/googletest/docs/AdvancedGuide.md.

Currently, Ament can only see the difference between pass/fail, which is good enough; but it would be great to have the ament test_results command work to see what specific tests failed, and how they failed. Currently, that command does not work because the Catch JUnit XML does not contain all of the tags that the GTest XML adds.

Extra information

Currently, the ament test_results command fails with the message

Skipping 'build\[path\to\output\folder]\[file].catchtest.xml': KeyError: 'tests'

Presumably, this is the Python KeyError exception, being thrown because the root node of the file does not contain the attribute 'tests'.

As stated above, this is not a mission-critical kind of thing; I'm happy to just look through the XML reports, but it would be super convenient if Catch could be used in places that expect GTest format.

  • Catch version: v2.2.1
  • Operating System: Windows 10
  • Compiler+version: Microsoft Visual Studio Compiler 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant