[
https://issues.apache.org/jira/browse/ZOOKEEPER-2223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14611688#comment-14611688
]
Akihiro Suda commented on ZOOKEEPER-2223:
-----------------------------------------
Jenkins (currently HTTP 503) for v2.patch failed because JUnit v3 (
{{junit.framework.*}} ) and JUnit v4 ( {{org.junit.*}} ) were jumbled together.
JUnit v3 throws {{junit.framework.AssertionFailedError}, however JUnit v3
throws {{java.lang.AssertionError}}.
This led Jenkins to fail.
I will eliminate all the JUnit v3 codes and run tests before committing to JIRA.
> support method-level JUnit testcase
> -----------------------------------
>
> Key: ZOOKEEPER-2223
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2223
> Project: ZooKeeper
> Issue Type: Improvement
> Components: tests
> Reporter: Akihiro Suda
> Assignee: Akihiro Suda
> Priority: Minor
> Attachments: ZOOKEEPER-2223-v2.patch, ZOOKEEPER-2223.patch
>
>
> Currently, a user can execute class-level single test, but cannot execute
> method-level ones.
> This patch adds a support for method-level single test so as to facilitate
> ease of debugging failing tests (like ZOOKEEPER-2080).
> Class-level test (exists in current version)
> {panel}
> $ ant -Dtestcase=ReconfigRecoveryTest test-core-java
> {panel}
> Method-level test (proposal)
> {panel}
> $ ant -Dtestcase=ReconfigRecoveryTest
> -Dtest.method=testCurrentObserverIsParticipantInNewConfig test-core-java
> {panel}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
