[
https://issues.apache.org/jira/browse/SLING-4322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated SLING-4322:
-----------------------------------
Attachment: SLING-4322-v1.diff
Attached is a patch which adds the stack trace to plain text and html
renderers. Also logging with level warn was added for all test failures on the
server side.
What is still missing is the JSON rendition (can we modify the JSON format?)
and it needs to be verified whether the XmlRenderer can also use
{{Failure.getTrace()}}.
[~bdelacretaz] Maybe you can have a look.
> 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
> Attachments: SLING-4322-v1.diff
>
>
> 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)
