We have a rich test framework around JUnit 4 allowing to declare RunnerFeature with callback methods called during a precise moment of the test.
This part of the framework suffers from exception swallowing making development harder in case of errors during before test phase.
We want to fix this swallowing issue, the root cause should be kept as it.
We don't want to wrap the exception each time we catch one because JUnit 4 has a chain mechanism (like Filter in servlet API) which will result in a chain of exception, this is not suitable for debugging.
Also, let's try to add some trace/debug logging for further analysis.