[jbosstools-issues] [JBoss JIRA] (JBIDE-11301) no stacktrace when junit tests fail
Alexey Kazakov (JIRA)
jira-events at lists.jboss.org
Fri May 4 13:48:18 EDT 2012
[ https://issues.jboss.org/browse/JBIDE-11301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12690503#comment-12690503 ]
Alexey Kazakov commented on JBIDE-11301:
----------------------------------------
I'm not sure.
This is not an AssertionFailedError which is usually thrown by assert() or fail() in tests.
Anyway I just ran our tests locally and still don't see the stacktrace in console. But maybe it works in Hudson?
> 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/job/jbosstools-3.3_trunk.component--cdi/lastCompletedBuild/console
> 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
More information about the jbosstools-issues
mailing list