Konrad Windszus created SLING-4322:
--------------------------------------
Summary: JUnit Core: All RunListeners should expose the stack
trace in case of test failures
Key: SLING-4322
URL: https://issues.apache.org/jira/browse/SLING-4322
Project: Sling
Issue Type: Improvement
Affects Versions: JUnit Core 1.0.10
Reporter: Konrad Windszus
Currently if a remote unit test fails on the client side you only see the
assertion message but not the stack trace (which could give more hints, why
exactly the test case failed).
By default the {{SlingRemoteTestRunner}} leverages the response of the
{{PlainTextRenderer}} to give out an error. The {{PlainTextRenderer}} currently
does not print the stack trace. It should rather do that via
{{Failure#getTrace()}} instead of just relying on {{Failure#toString()}}.
That should be done for all Renderers (to also ease debugging if the JUnit
servlet is directly called with a browser)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
