[
https://issues.apache.org/jira/browse/LUCENE-3489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121102#comment-13121102
]
Robert Muir commented on LUCENE-3489:
-------------------------------------
{quote}
Oh, by the way – is there any particular reason for so many things to be static
(class level)? I get these are fixtures reused by tests but would people scream
if they were object-level fixtures rather than class-level fixtures? It'd make
things a bit easier... starting with the need for a single initial seed, for
example.
{quote}
why we have the different seeds:
One thing we do is support running a test class (test1(), test2(), test3()). If
test2() fails, we want to be able to just run that method and reproduce it.
So we allow you to specify -Dtestmethod to only run a single method.
At the same time, we want to support doing things like creating indexes in
beforeClass() and afterClass() for efficient tests.
We also support -Dtests.iter, where you run a single test method over and
over... this is often convenient. If we only had 1 class-level seed, this would
be useless as it would just do the same thing over and over!
So the need for multiple seeds comes from the fact that some things are random
at "class-level" and some things are at "method level".
If you look at the 3 parts to the random seed, its really part1:part2:part3,
* part1 = class seed
* part2 = method seed
* part3 = runner seed (this is needed for consistent randomization of test
methods)
> Refactor test classes that use assumeFalse(codec != SimpleText, Memory) to
> use new annotation and move the expensive methods to separate classes
> ------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: LUCENE-3489
> URL: https://issues.apache.org/jira/browse/LUCENE-3489
> Project: Lucene - Java
> Issue Type: Test
> Components: general/test
> Affects Versions: 4.0
> Reporter: Uwe Schindler
> Fix For: 4.0
>
>
> Folloup for LUCENE-3463.
> TODO:
> - Move test-methods that need the new @UseNoMemoryExpensiveCodec annotation
> to separate classes
> - Eliminate the assumeFalse-calls that check the current codec and disable
> the test if SimpleText or Memory is used
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
