Improvement #1964
Better handling of non-serializable server-side throwables in Z2UnitTestRunner
Start date:
27.01.2017
Due date:
% Done:
0%
Estimated time:
origin:
Description
Currently, when running into a de-serialization failure upon handling exceptions that fail to
de-serialize on the client, only a message is shown and the actual error text is lost.
- On server-side also add the StackTrace to the failure json
- On the client, if de-serialization failed, add a wrapper exception with the original text.
Related issues
Updated by Henning Blohm about 7 years ago
- Related to Bug #1946: Z2UnitTestRunner absorbs InitializationError from org.junit.runners.ParentRunner added