gtest XML output lacks namespace about ros HOT 2 CLOSED

I fully agree with you observation that the test results shown in Jenkins are not giving you any indicator where the tests are coming from.

I am not very keen to encode the package name into every gtest within that package. Simply because from a design point I don't think the test should know about it and the developer shouldn't need to repeat that information.

When you look at the generated JUnit / xUnit result files and where they are being generated you will notice that they are being generated in a subfolder named after the package. The problem of the Jenkins UI in my opinion is that it doesn't show you that file path. With that information you would know immediately from which package the test came from and even in which test group it is (e.g. a launch file or a specific gtest file).

It would be nice if the Jenkins plugin would be improved to actually show where the test result came from. That would help if you are looking at a specific result. But that wouldn't provide the nice hierarchy as for the Python tests (where you click on the package name first, and then the next level shows you the tests in there). So extending the mangling logic in the xml post-processing step to prefix gtest results with the package name are the only way to achieve that as far as I know.

from ros.

Closing due to no activity.

from ros.