lucene-dev mailing list archives

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


Hoss Man commented on SOLR-3826:

bq. I didn't know this was a constant so I'll give a shot to find it and reference it.

yeah, it dates back to the fact that solr will still work with "pre-multicore" solr home dirs
that are really just single SolrCore instance dirs -- in which case it refers to the core
as "collection1" ... the constant you want is CoreContainer.DEFAULT_DEFAULT_CORE_NAME  (which
this test code should have been using in the first place, but as long as we're touching it
let's fix it)

bq. Are there any existing docs about how to create tests with Solr? I found there was some
discussion on the mailing list. I'm happy to take a first pass at this if you think it'd help.

As far as i know the only docs are the javadocs in the base classes and test harness -- if
you'd like to take a stab at adding useful content to solr/test-framework/src/java/overview.html
that would be awesome! (but perhaps deal with thta in a separate jira/patch so it doesn't
hold up this already useful fix?)
> 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