Bug 452022

Summary:	[JUnit] Don't hide failure message on initialization error
Product:	[Eclipse Project] JDT	Reporter:	Moritz Eysholdt <moritz.eysholdt>
Component:	UI	Assignee:	JDT-UI-Inbox <jdt-ui-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	daniel_megert, noopur_gupta
Version:	4.5	Keywords:	bugday
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:	stalebug

Description Moritz Eysholdt

2014-11-18 04:07:41 EST

Version: N20141116-2000 (including fix for bug 443498)

When test execution fails with an initialization error, e.g. because the test-method doesn't exist, and "Filter Stack Trace" is enabled (default), the error message is not shown.

Steps to reproduce:

Launch the test by explicitly launching "other() from":
---
public class FooTest {

	@Test
	public void test() {
	}

	public void other() {
	}
}
---

The JUnit-View's Tree View will show a single item named "initializationError".

The Failure Trace area is empty if "filter failure trace" is enabled.
I would expect that at least the Exception's message is shown to the user. 

For the example from above the message is "No Tests found matching". That is valuable information for the user since otherwise the reason for the initalizationError remains a mystery.

Comment 1 Moritz Eysholdt

2014-11-18 04:08:55 EST

(In reply to Moritz Eysholdt from comment #0)
> Launch the test by explicitly launching "other() from":

This should have been:
Launch the test by explicitly launching "other()" from:

Comment 2 Dani Megert

2014-11-28 04:36:03 EST

Moritz, do you want to take this bug?

Comment 3 Eclipse Genie

2020-03-18 18:23:15 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.