You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2013/10/31 08:09:26 UTC

[jira] [Assigned] (SLING-3000) Support propagation of executing testName to server

     [ https://issues.apache.org/jira/browse/SLING-3000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chetan Mehrotra reassigned SLING-3000:
--------------------------------------

    Assignee: Chetan Mehrotra

> 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
>         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)