[
https://issues.apache.org/jira/browse/SUREFIRE-1042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Jefferson updated SUREFIRE-1042:
-------------------------------------
Attachment: test.zip
Not sure why a "test" is required for such basic behaviour but anyway. The
attached simple maven project has a single Java class to compile, and single
test (which simply calls JUnit fail to simulate a failing test). The console
output is
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.033 sec <<<
FAILURE! - in mydomain.test.SimpleTest
testSimple(mydomain.test.SimpleTest) Time elapsed: 0.003 sec <<< FAILURE!
java.lang.AssertionError: Failed test : is failed for some reason or other
at org.junit.Assert.fail(Assert.java:93)
at mydomain.test.SimpleTest.testSimple(SimpleTest.java:14)
Results :
Failed tests:
SimpleTest.testSimple:14 Failed test : is failed for some reason or other
THIS IS REGARDLESS OF USE (or not) OF -Dmaven.test.redirectTestOutputToFile=true
Perhaps now some way can be provided to get old behaviour? Thanks!
> 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
> 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)
