You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2016/04/21 23:50:13 UTC
[jira] [Commented] (SOLR-8758) Add SolrCloudTestCase base class
[ https://issues.apache.org/jira/browse/SOLR-8758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15252819#comment-15252819 ]
ASF subversion and git services commented on SOLR-8758:
-------------------------------------------------------
Commit 27e284bb7bcd6536b3c017d76e675f24397cce9c in lucene-solr's branch refs/heads/branch_5x from [~romseygeek]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=27e284b ]
SOLR-8758: Add SolrCloudTestCase base class
> Add SolrCloudTestCase base class
> --------------------------------
>
> Key: SOLR-8758
> URL: https://issues.apache.org/jira/browse/SOLR-8758
> Project: Solr
> Issue Type: Improvement
> Reporter: Alan Woodward
> Fix For: 6.0, 5.5.1
>
> Attachments: SOLR-8758.patch
>
>
> At the moment, if you want to write unit tests for Cloud components, you have to extend AbstractDistribZkTestCase, which has a number of disadvantages:
> * the API isn't well-documented
> * you get a default configuration loaded into ZK, and it's not trivial to add separate ones
> * you get a default collection, whether you want one or not
> * the test cluster isn't static, which means that it's started up and shutdown after every test function. To avoid tests being incredibly slow, we end up writing single-function tests that call out to sub-functions, losing the benefits of execution-order randomization.
> It would be more useful to have a properly configurable and documented testcase base class.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org