[
https://jira.codehaus.org/browse/SUREFIRE-1017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=329489#comment-329489
]
Christian Spriegel commented on SUREFIRE-1017:
----------------------------------------------
I sure do :-) These roundtrips always contain some other files along with the
RoundtripTest.java, so I put each test in a separate package. Therefore there
is no need to rename the class.
Thanks for your quick response. Any chance to get the ticket scheduled for 2.16?
What about a option to allow configuring the output? Maybe something like this:
{code}
<summaryReport>package,class,method,line,exception</summaryReport>
{code}
But I'm also fine with an automatic detection.
> Failures do not show test-package since 2.13
> --------------------------------------------
>
> Key: SUREFIRE-1017
> URL: https://jira.codehaus.org/browse/SUREFIRE-1017
> Project: Maven Surefire
> Issue Type: Improvement
> Affects Versions: 2.13, 2.14, 2.15
> Reporter: Christian Spriegel
>
> Older versions of surefire always showed the package name of each failed test
> in the result overview.
> Since surefire 2.13 I simply get the classname:
> {code}
> Results :
> Failed tests:
> RoundtripTest>AbstractTestNGSpringContextTests.run:196->test:115 error
> RoundtripTest>AbstractTestNGSpringContextTests.run:196->test:115 error
> {code}
> As you can see I have two tests called RoundtripTest in the overview. These
> testclasses are in different packages, but I do not know which one is which.
> My testsuite has 830 testcases, where ~650 are called RoundtripTest. So its
> quite hard now for me to identify the failing tests.
> SUREFIRE-936 seems to have changed this. I have not checked the git commit,
> but from the description I assume that was the change.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
