[
https://issues.apache.org/jira/browse/SLING-4280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz updated SLING-4280:
---------------------------------------
Attachment: EventsCounter.patch
Ok, thanks for the clarifications, I understand the issue now.
+1 for committing, I've been able to use this feature with the attached
EventsCounter.patch that creates a failing test.
Maybe the sling.test.* HTTP headers should start with the X- prefix for
non-standard headers? If changing this note that there are several definitions
of their names.
I have updated the test-bundles module in revision 1651103, to use the latest
junit.core bundle that includes the TestLogServlet.
> Enable dumping of remote server logs in case of test failures
> -------------------------------------------------------------
>
> Key: SLING-4280
> URL: https://issues.apache.org/jira/browse/SLING-4280
> Project: Sling
> Issue Type: New Feature
> Components: Testing
> Reporter: Chetan Mehrotra
> Assignee: Chetan Mehrotra
> Attachments: EventsCounter.patch, SLING-4280.patch,
> test-fail-output.txt
>
>
> In case of large test suite running on CI server its hard to make out which
> logs were created due to execution of which testcase. This makes determining
> the cause of testcase failure difficult. Often the server logs are also not
> avialable once the build is completed and only source of information is
> system out logs captured via junit framework on client side.
> This debugging process can be made simpler if the testcase also dumps the
> server side logs generated while that testcase executes locally upon failure
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
