We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug A test of the form:
namespace foo { class bar {}; } TEST_CASE_METHOD(foo::bar, "test")
using the junit reporter creates an output in the form
junit
<testcase classname="test.exe.foo::bar" name="test" time="0.002" status="run"/>
The classname is mal-formed, a Java classpath like identifier was expected, but a C++ like class path is yielded instead.
classname
Expected behavior
<testcase classname="test.exe.foo.bar" name="test" time="0.002" status="run"/>
The C++ style class path is translated properly into a Java style class path by substituting any :: in testInfo.className with ..
::
testInfo.className
.
This allows Jenkins and Gitlab to properly group tests by namespace hierarchy as expected.
The text was updated successfully, but these errors were encountered:
Normalize C++ namespace in JUnit's reporter classname field
7b2fafd
Closes #2468
9c9f350
No branches or pull requests
Describe the bug
A test of the form:
using the
junit
reporter creates an output in the formThe
classname
is mal-formed, a Java classpath like identifier was expected, but a C++ like class path is yielded instead.Expected behavior
The C++ style class path is translated properly into a Java style class path by substituting any
::
intestInfo.className
with.
.This allows Jenkins and Gitlab to properly group tests by namespace hierarchy as expected.
The text was updated successfully, but these errors were encountered: