You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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
The text was updated successfully, but these errors were encountered:
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 messagePresumably, 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.
The text was updated successfully, but these errors were encountered: