[
https://issues.apache.org/jira/browse/SUREFIRE-1042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15054257#comment-15054257
]
Andreas Gudian commented on SUREFIRE-1042:
------------------------------------------
I wouldn't mix the way of displaying the stack trace on the console with the
parameter {{redirectTestOutputToFile}} - as the stacktrace itself in this case
is not printed by the test, but by our console reporter.
My guess would also be that it came in with {{trimStackTrace}} - or a change in
that area. Currently, we don't have an option to control the output format
there (no stacktrace, trimmed stacktrace, or full stacktrace). So that might be
a way to go. But I guess understanding when and why the change was made in in
the first place would do us some good here... ;)
As we have the current behaviour for some years now (2.16 is quite some time
ago), we shouldn't just switch back to the default behaviour we had before that.
> Provide way of running tests so that stack trace isn't dumped onto console
> --------------------------------------------------------------------------
>
> Key: SUREFIRE-1042
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1042
> Project: Maven Surefire
> Issue Type: Bug
> Affects Versions: 2.13, 2.14, 2.15, 2.16
> Environment: Maven 3.x, Linux
> Reporter: DN
> Assignee: Tibor Digana
> Attachments: test.zip
>
>
> We never used to get stack traces from any failed tests (asserts) being
> dumped onto the console. "Upgrading" to 2.16 means that they now get dumped
> onto the console (UGLY IMHO). Can we at least have the option of the previous
> output behaviour (2.10 for example)? If there already is a way of achieving
> this, please advise, I couldn't find anything that had an effect.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
