[jbosstools-issues] [JBoss JIRA] (JBIDE-11301) no stacktrace when junit tests fail

[Mickael Istria (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-11301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12690371#comment-12690371 ] 

Mickael Istria commented on JBIDE-11301:
----------------------------------------

Alexey,

When I look at this build: https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/job/jbosstools-3.3_trunk.component--cdi/1097/consoleFull
I see the following

{code}
-------------------------------------------------------
 T E S T S
-------------------------------------------------------
Running org.jboss.tools.cdi.core.test.CDICoreAllTests
Exception in thread "Thread-6" java.lang.NullPointerException
	at org.jboss.tools.common.java.ParametedType.findParameter(ParametedType.java:302)
	at org.jboss.tools.common.java.ParametedTypeFactory.getParametedType(ParametedTypeFactory.java:85)
	at org.jboss.tools.common.java.ParametedType.buildInheritance(ParametedType.java:183)
	at org.jboss.tools.common.java.ParametedType.getInheritedTypes(ParametedType.java:229)
	at org.jboss.tools.common.java.ParametedType.buildAllTypes(ParametedType.java:319)
	at org.jboss.tools.common.java.ParametedType.buildAllTypes(ParametedType.java:321)
	at org.jboss.tools.common.java.ParametedType.buildAllTypes(ParametedType.java:321)
	at org.jboss.tools.common.java.ParametedType.buildAllTypes(ParametedType.java:321)
	at org.jboss.tools.common.java.ParametedType.buildAllTypes(ParametedType.java:321)
	at org.jboss.tools.common.java.ParametedType.getAllTypes(ParametedType.java:307)
	at org.jboss.tools.cdi.core.test.TypeTest$R.run(TypeTest.java:76)
	at java.lang.Thread.run(Thread.java:662)
Running Update class path of kb project RemoveJarTest
Running Update class path of kb project RemoveJarTest
2
void addEntry(Object) [in ClassFragmentLogger [in ClassFragmentLogger.java [in org.jboss.jsr299.tck.tests.jbt.validation.observers [in JavaSource [in tck]]]]]
void observeObject(Object) [in EventTypeFamilyObserver [in EventTypeFamilyObserver.java [in org.jboss.jsr299.tck.tests.event.eventTypes [in JavaSource [in tck]]]]]
Tests run: 432, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 288.383 sec <<< FAILURE!

Results :

Failed tests:   testType(org.jboss.tools.cdi.core.test.TypeTest): expected:<11> but was:<0>

Tests run: 432, Failures: 1, Errors: 0, Skipped: 0
{code}

Does this output mean this issue is fixed or do you expect more?

                
> 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