[
https://jira.codehaus.org/browse/SUREFIRE-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=363407#comment-363407
]
Karl-Heinz Marbaise commented on SUREFIRE-1142:
-----------------------------------------------
The problem here is that maven-surefire-plugin is more or less in the middle of
the life-cycle (test and afterwards prepare-package, package, etc.) in
contradiction to maven-deploy-plugin (with deployAtEnd) which is the end of the
life cycle.
So the result would be having a large number of modules
{code}
...Test runs
...
FAILED TESTS...
..
maven-install...
..
maven-deploy...
...
List of reactor
...
{code}
The only real working solution (or better to get the wished output at the end
of the build) would be an EventSpy which unfortunately is not a plugin...I have
worked on something similar for analyzsis of tests
https://github.com/khmarbaise/maven-test-profiler which produces something like
this...(First working version; currently working but not ready yet).
> Summarize at End in multimodule projects
> ----------------------------------------
>
> Key: SUREFIRE-1142
> URL: https://jira.codehaus.org/browse/SUREFIRE-1142
> Project: Maven Surefire
> Issue Type: New Feature
> Reporter: Andreas Gudian
>
> In multimodule projects with {{testFailureIgnore=true}}, it is very tedious
> to find out if / where there were any test failures when building on the
> console. Our HTML report format is of no real help there either.
> I suggest to display the test summary of failing tests at the end of the
> reactor build (or after the last of the reactor projects) in case
> {{testFailureIgnore=true}}.
> Implementation-wise, we can do it like install / deploy do it with their
> {{installAtEnd}} / {{deployAtEnd}} options.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
