Hello,
Could you give me some advice or comments about usage of LuceneTestCase.
Some of our unit tests extending LuceneTestCase fail by assertion error --
sometimes, randomly.
I suppose we use LuceneTestCase in inappropriate way, but cannot find out
how to fix it.
Here is some information about
I was running these luke tests a bunch and found the following tests fail
intermittently; pretty frequently. Once I @Ignore them I can get a
consistent pass:
CommitsImplTest.testListCommits
CommitsImplTest.testGetCommit_generation_notfound
CommitsImplTest.testGetSegments
Thanks a lot for your information & insights,
I will try to reproduce the errors and investigate the results.
And, maybe I should learn more about internal of the test framework,
I'm not familiar with it and still do not understand what does "seed" means
exactly in this context.
Regards,
Tomoko
The pseudo-random generator in the Lucene test framework is used to
randomize lots of test conditions, we're talking about the file system
implementation here, but there are lots of others. Whenever you see a
call to random().whatever, that's the call to the framework's method.
But here's the
Couple of things (and I know you've been around for a while, so pardon
me if it's all old hat to you):
1> if you run the entire "reproduce with" line and can get a
consistent failure, then you are half way there, nothing is as
frustrating as not getting failures reliably. The critical bit is
Hi, Mike
Thanks for sharing your experiments.
> CommitsImplTest.testListCommits
> CommitsImplTest.testGetCommit_generation_notfound
> CommitsImplTest.testGetSegments
> DocumentsImplTest.testGetDocumentFIelds
I also found CommitsImplTest and DocumentsImplTest fail frequently,
especially
