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

Andy Jefferson commented on SUREFIRE-1042:
------------------------------------------

[~tibor17]
Well that removes the stack trace BUT also removes the test by test listing. 
For example, when I have 2 test classes I get the following with v2.10

-------------------------------------------------------
 T E S T S
-------------------------------------------------------
Running mydomain.test.Simple2Test
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.036 sec
Running mydomain.test.SimpleTest
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.001 sec <<< 
FAILURE!

Results :

Failed tests:   testSimple(mydomain.test.SimpleTest): Failed test : is failed 
for some reason or other

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

but with this config and 2.16+ I get 
-------------------------------------------------------
 T E S T S
-------------------------------------------------------
Failed tests: 
  SimpleTest.testSimple:14 Failed test : is failed for some reason or other

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


So no, that is not acceptable really. It loses too much info that is seen as 
the tests run

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

Reply via email to