[
https://issues.apache.org/jira/browse/ZOOKEEPER-2223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14616141#comment-14616141
]
Raul Gutierrez Segales commented on ZOOKEEPER-2223:
---------------------------------------------------
Oh, forget the question about computeTestMethodsForClass being public and
static — I didn't see src/java/test/org/apache/zookeeper/ZKParameterized.java
when I applied the patch locally. I still do wonder why the 2nd parameter is
reassigned and how we can make that more obvious (if not do without it at all).
> 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-v3.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)
