You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@zookeeper.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2010/04/02 23:39:27 UTC

[jira] Commented: (ZOOKEEPER-724) Improve junit test integration - log harness information

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12852961#action_12852961 ] 

Hudson commented on ZOOKEEPER-724:
----------------------------------

Integrated in ZooKeeper-trunk #777 (See [http://hudson.zones.apache.org/hudson/job/ZooKeeper-trunk/777/])
    

> Improve junit test integration - log harness information
> --------------------------------------------------------
>
>                 Key: ZOOKEEPER-724
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-724
>             Project: Zookeeper
>          Issue Type: Improvement
>          Components: tests
>            Reporter: Patrick Hunt
>            Assignee: Patrick Hunt
>             Fix For: 3.4.0
>
>         Attachments: ZOOKEEPER-724.patch
>
>
> Currently we have ad-hoc logging (log4j) of setup/teardown and test start/end. Without this information it's often difficult to determine
> what's going on (major milestones) in the logs relative to the tests performed.
> In junit 4.x "@Rule" annotations have been added that allow this to be done much more easily. This patch will add this.
> In particular we can access the test name easily during setup/teardown and the test itself. Additionally we can log more information on
> success/failure of each test.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.