Community
Participate
Working Groups
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.
(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:
Moritz, do you want to take this bug?
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.
