mirrors/cdt
1
0
Fork 0
mirror of https://github.com/eclipse-cdt/cdt synced 2025-07-04 15:45:25 +02:00
Code Issues Wiki Activity

[219069] Improved error reporting for exceptions in event loop while running junit plug-in tests

Browse source
This commit is contained in:
Martin Oberhuber 2008-02-15 12:34:17 +00:00
parent 50ded2aa5f
commit 3f5b5027d7
1 changed files with 11 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

13
rse/tests/org.eclipse.rse.tests/src/org/eclipse/rse/tests/subsystems/testsubsystem/TestSubsystemTestCase.java
View file

@ -15,6 +15,8 @@ package org.eclipse.rse.tests.subsystems.testsubsystem;
import java.util.Vector;
import junit.framework.AssertionFailedError;
import org.eclipse.jface.viewers.AbstractTreeViewer;
import org.eclipse.rse.core.RSECorePlugin;
import org.eclipse.rse.core.events.ISystemResourceChangeEvents;
@ -203,8 +205,15 @@ public class TestSubsystemTestCase extends RSEBaseConnectionTestCase {
RSEWaitAndDispatchUtil.waitAndDispatch(10000);
}
catch (Exception e) {
e.printStackTrace();
assertNull(e.getMessage(), e);
//We cannot have the Exception forwarded to the test framework, because
//it happens in the dispatch thread and our Runnable.run() method does
//not allow checked exceptions. Therefore, convert the exception into
//an Error that the test framework can handle, but make sure that the
//cause of the Error (the original exception) is maintained by calling
//initCause(). This will allow seeing it in the JUnit runner later on.
Error err = new AssertionFailedError("Unhandled event loop exception");
err.initCause(e);
throw err;
}
}
}