[ 
https://issues.apache.org/jira/browse/LUCENE-2764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12932559#action_12932559
 ] 

Robert Muir commented on LUCENE-2764:
-------------------------------------

bq. Eventually we would want to enable users to plug in their codecs into the 
RandomCodecProvider to test it against all our testcases. I think that should 
be a separate issue though.

I don't think we should do this.
Our src/test shouldn't be a setup for people to test arbitrary extensions to 
lucene such as Directories or Codecs.
If it happens to work that they can simply edit a file and test these things, 
thats great, but we shouldnt officially support this in src/test.
src/test is no-holds-barred just doing the best we can to test lucene itself... 
it should stick to this level of scope.

if we want to provide mechanisms to test arbitrary user extensions it should be 
supported and documented in src/java like LockStressTest. 


> Allow tests to use random codec per field
> -----------------------------------------
>
>                 Key: LUCENE-2764
>                 URL: https://issues.apache.org/jira/browse/LUCENE-2764
>             Project: Lucene - Java
>          Issue Type: Test
>          Components: Tests
>    Affects Versions: 4.0
>            Reporter: Simon Willnauer
>            Priority: Minor
>             Fix For: 4.0
>
>         Attachments: LUCENE-2764.patch, LUCENE-2764.patch
>
>
> Since we now have a real per field codec support we should enable to run the 
> tests with a random codec per field. When I change something related to 
> codecs internally I would like to ensure that whatever combination of codecs 
> (except of preflex) I use the code works just fine. I created a 
> RandomCodecProvider in LuceneTestCase that randomly selects the codec for 
> fields when it sees them the first time. I disabled the test by default to 
> leave the old randomize codec support in as it was / is.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to