[jira] [Comment Edited] (SUREFIRE-1042) Provide way of running tests so that stack trace isn't dumped onto console

["Tibor Digana (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SUREFIRE-1042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15043806#comment-15043806 ] 

Tibor Digana edited comment on SUREFIRE-1042 at 12/6/15 10:35 AM:
------------------------------------------------------------------

[~andy]
Can you attach Maven project to reproduce it?
Otherwise we will close it.


was (Author: tibor17):
[~andy]
Can you attache Maven project to reproduce it?
Otherwise we will close it.

> 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
>
> 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)