maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tibor Digana (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SUREFIRE-1042) Provide way of running tests so that stack trace isn't dumped onto console
Date Tue, 08 Dec 2015 22:32:11 GMT

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

Tibor Digana commented on SUREFIRE-1042:
----------------------------------------

[~andy]
I think you can switch off the stack trace with this configuration. Are you satisfied with
that?

          <redirectTestOutputToFile>true</redirectTestOutputToFile>
          <printSummary>false</printSummary>


-------------------------------------------------------
 T E S T S
-------------------------------------------------------
Failed tests: 
  FooTest.t:48 null

Tests run: 1, Failures: 1, Errors: 0, Skipped: 0

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

Mime
View raw message