[
https://issues.apache.org/jira/browse/ZOOKEEPER-2223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14608904#comment-14608904
]
Chris Nauroth commented on ZOOKEEPER-2223:
------------------------------------------
+1 (non-binding) pending a Jenkins run. Good idea, [~suda]! I applied the
patch locally and tested running a single test method.
Just to make sure it's clear to everyone, this only works for test suites that
use {{JUnit4ZKTestRunner}}. It won't work for suites that use the default
runner (i.e. {{WatchesSummaryTest}}) or parameterized suites (i.e.
{{RemoveWatchesTest}}). It's still useful though.
> 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.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)
