lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <>
Subject [jira] [Assigned] (SOLR-3826) Allow unit test classes to specify core name during setup
Date Thu, 13 Sep 2012 23:18:08 GMT


Hoss Man reassigned SOLR-3826:

    Assignee: Hoss Man

Concept looks sound, but i'd like to replace that test specific "collection1" constant with
a refrence to the existing place where it's defined as the default collection name (in CoreContainer
i believe) as well as add some javadocs to the test harness/baseclass about the assumption.

Amit: if you'd like to take a stab at those improvements before i get a chance, that would
be awesome
> Allow unit test classes to specify core name during setup
> ---------------------------------------------------------
>                 Key: SOLR-3826
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>          Components: Build
>    Affects Versions: 4.0-BETA
>            Reporter: Amit Nithian
>            Assignee: Hoss Man
>            Priority: Minor
>             Fix For: 4.0
>         Attachments: SOLR-3826.patch
> When creating a unit test extending SolrTestCaseJ4, the corename is forced to "collection1"
which can be problematic if you want to do unit tests relying on schema/solrconfig specific
to a core. Rather than hard-coding to "collection1" allow this to be specified in the initCore

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message