[jbosstools-issues] [JBoss JIRA] (JBIDE-11301) no stacktrace when junit tests fail
[
https://issues.jboss.org/browse/JBIDE-11301?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-11301:
---------------------------------------------
relevant comment in tycho git repo:
" 367778 TestMojo: don't redirect console to file by default
Revert to old default behaviour which prints console
logs from tests to System.out by default.
Make test output redirection to file configurable
using TestMojo parameter "redirectTestOutputToFile",
same as maven-surefire-plugin, see [1]
[1]
http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html#redi...
no stacktrace when junit tests fail
-----------------------------------
Key: JBIDE-11301
URL: https://issues.jboss.org/browse/JBIDE-11301
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, UpStream
Affects Versions: 3.3.0.Beta3
Reporter: Alexey Kazakov
Assignee: Mickael Istria
Priority: Minor
Fix For: 3.3.x
If I run JBT tycho build locally for trunk, for example:
mvn clean install -fae -e -P default -f cdi/tests/pom.xml
and there is some test failures then I don't see any stacktrace in console. Just a
text message from the JUnit test assert.
-Dsurefire.useFile=false does not help.
But I see the stacktrace in <target>/surefire-reports
In Beta1 branch it works fine.
I don't see stacktrace in console output in Hudson either but I'm not sure
it's a problem there.
For example
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo...
But for local builds it's very useful to see the full stacktrace in console.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira