[
https://issues.apache.org/jira/browse/ZOOKEEPER-724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Hunt updated ZOOKEEPER-724:
-----------------------------------
Attachment: ZOOKEEPER-724.patch
this patch cleans up the tests by:
1) moving everything over to junit4 fully (annotations)
2) added a test runner subclass that all the tests use - this runner logs
(log4j) before/after running a test method
3) adds a test watchman (@rule) that logs before/after a test is run, also logs
test result - success/failure, and in the case of failure the exception that
caused the failure
basically this allows us to much more easily track when tests start/end and
setup/teardown runs.
> 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.
