lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (JIRA)" <>
Subject [jira] Commented: (LUCENE-2598) allow tests to use different Directory impls
Date Thu, 12 Aug 2010 11:24:17 GMT


Robert Muir commented on LUCENE-2598:

bq. Robert, how about if we use JUnit's TemporaryFolder (

Hi Shai, I looked at this, but I don't think we should use it. I think we should keep a consistent
API between LuceneTestCase and LuceneTestCase4J.

But this TemporaryFolder is too basic for our needs and does not support our usage of LuceneTestCase4J
(where the index is created in @beforeClass and destroyed in @afterClass),
it only supports removing the directory after each test METHOD.

Furthermore, there is no way to tell junit where to put this TemporaryFolder. Right now ensure
that tests don't stomp on each others feet by giving
them unique temp directories per-jvm, i would like to continue ensuring that any temporary
data is placed there, not somewhere randomly on the users system.
This way all data created by 'ant test' is guaranteed to be removed in 'ant clean'.

> allow tests to use different Directory impls
> --------------------------------------------
>                 Key: LUCENE-2598
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Test
>          Components: Build
>    Affects Versions: 3.1, 4.0
>            Reporter: Robert Muir
>            Assignee: Robert Muir
>             Fix For: 3.1, 4.0
> Now that all tests use MockRAMDirectory instead of RAMDirectory, they are all picky like
windows and force our tests to
> close readers etc before closing the directory.
> I think we should do the following:
> # change new MockRAMDIrectory() in tests to .newDirectory(random)
> # LuceneTestCase[J4] tracks if all dirs are closed at tearDown and also cleans up temp
dirs like solr.
> # factor out the Mockish stuff from MockRAMDirectory into MockDirectoryWrapper
> # allow a -Dtests.directoryImpl or simpler to specify the default Directory to use for
tests: default being "random"
> i think theres a chance we might find some bugs that havent yet surfaced because they
are easier to trigger with FSDir
> Furthermore, this would be beneficial to Directory-implementors as they could run the
entire testsuite against their Directory impl, just like codec-implementors can do now.

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:
For additional commands, e-mail:

View raw message