You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Patrick Hunt (JIRA)" <ji...@apache.org> on 2010/03/24 06:52:27 UTC
[jira] Updated: (ZOOKEEPER-724) Improve junit test integration -
log harness information
[ https://issues.apache.org/jira/browse/ZOOKEEPER-724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Hunt updated ZOOKEEPER-724:
-----------------------------------
Status: Patch Available (was: Open)
> 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.