[GRADLE-2649] Test report uses suite class name instead of implementation class name for tests run via @RunWith(Suite.class). Created: 21/Jan/13 Updated: 24/Feb/14 Resolved: 29/Jan/13
|Comment by Peter Niederwieser [ 01/Feb/13 ]|
I think we should show both the suite and its constituents (i.e. add one additional level). This is how suites are modelled in JUnit, how they are commonly thought of, how they are displayed by IDEs, and AFAIK also how we report them via the test listener.
|Comment by Adam Murdoch [ 02/Feb/13 ]|
Absolutely. That's the next story.
|Comment by Remy de Wolf [ 24/Feb/14 ]|
we recently upgraded from gradle 1.4 to 1.9 and along the way found this issue related to the generation of the junit XML reports.
We have organized our tests in multiple sub projects.
With gradle 1.4, junit XML report file names use suite class names which would create such an output:
When updating to gradle 1.9 the xml report file name have changed to use implementation class and are not unique anymore:
The issue with gradle 1.9 is that the test reports are not unique and it creates some incorrect test reporting on CI servers.
As Peter commented in the Jira, test file names can be made unique by including both the suite and its constituents.