[
https://issues.apache.org/jira/browse/SLING-3000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chetan Mehrotra resolved SLING-3000.
------------------------------------
Resolution: Fixed
Fix Version/s: org.apache.sling.testing.tools 1.0.8
Applied the updated patch with revision http://svn.apache.org/r1537052
> Support propagation of executing testName to server
> ---------------------------------------------------
>
> Key: SLING-3000
> URL: https://issues.apache.org/jira/browse/SLING-3000
> Project: Sling
> Issue Type: Improvement
> Components: Testing
> Affects Versions: org.apache.sling.testing.tools 1.0.6
> Reporter: Chetan Mehrotra
> Assignee: Chetan Mehrotra
> Priority: Minor
> Fix For: org.apache.sling.testing.tools 1.0.8
>
> Attachments: SLING-3000-2.patch, SLING-3000.patch
>
>
> 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. If we have some way to
> propagate the testName to server then the testname can be exposed as part of
> MDC [1] and made part of logged statement
> Currently Sling Logging does not support MDC but at minimum we can have a
> filter which can log the test name extracted from HTTP Header allowing a user
> to correlate the logs with testcase failures
> [1] http://www.slf4j.org/manual.html#mdc
--
This message was sent by Atlassian JIRA
(v6.1#6144)
