You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-commits@lucene.apache.org by Apache Wiki <wi...@apache.org> on 2011/05/03 03:41:15 UTC

[Lucene-java Wiki] Update of "TestIdeas" by RobertMuir

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Lucene-java Wiki" for change notification.

The "TestIdeas" page has been changed by RobertMuir.
The comment on this change is: LUCENE-3064.
http://wiki.apache.org/lucene-java/TestIdeas?action=diff&rev1=16&rev2=17

--------------------------------------------------

   1. Add @Weekly, and turn it on for Test2BTerms
   1. Add getNumThreads() to LuceneTestCase that takes Runtime.getRuntime().availableProcessors() into account. Multi-threaded tests should use more threads than available processors to increase the chance to detect timing -sensitive data races so that at any given time some threads are running and some are switched out, thus reducing the predictability of interactions between threads.
   1. REALTIME_BRANCH - Add Random DWPTThreadPool that randomly assigns ThreadStates to increase test coverage in DW if tests are single threaded.
-  1. MockTokenizer should not extend CharTokenizer (this should move to analyzers module). Instead, it should extend Tokenizer directly. This way, we can add some extra asserts checks, for example the ctor and reset(Reader) could set resetCalled = false, but reset() would set this to true, and we assert it in incrementToken(). Because most tests use MockAnalyzer, checks like this can enforce that they are consuming tokenstreams correctly.
   1. MockDirectoryWrapper.close should also fail if there are still open files for writing (now it only fails if there are open files for reading)
   1. MockDirectoryWrapper should randomly swap in ThrottledIndexOutput (after RT branch lands)