[
https://issues.apache.org/jira/browse/LUCENE-3615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13162986#comment-13162986
]
Hoss Man commented on LUCENE-3615:
----------------------------------
bq. Because of this, all of the tests behave in totally different ways that you
cant really assign a weight to, e.g. take a look at the history of test times
for this test:
"Weight" may be the wrong term... i wasn't suggesting that it would be any sort
of quantitative, comparable metric of how long the test would take -- my point
was just that having a numeric annotation where bigger means "this test does
more stuff" would allow people to run more or less tests as they see fit with
simple configuration, regardless of whether their idea of a test to be run
"Nightly" jives directly with the @Nightly annotation (maybe i want to only run
@Nightly tests on weekends?)
As things stand, we have regular tests, and then we have @Nightly tests, and
then we have @Slow tests ... hypothetically: if we add a new test later that's
not nearly as bad as Test2BTerms, so we still want it to run as part of a "full
test run" but is bad enough that we don't want to jenkins to do it was part of
our "@Nightly" run, we have to consider some intermediate "@SortOfSlow"
attribute ... hence my suggestion that instead of adding more special case
annotations (and more build params for deciding when to exececute what), we
just use an arbitrary range of numbers and two simple "min" and "max" build
params to pick the tests to run.
...anyway ... it was just an idea.
> Make it easier to run Test2BTerms
> ---------------------------------
>
> Key: LUCENE-3615
> URL: https://issues.apache.org/jira/browse/LUCENE-3615
> Project: Lucene - Java
> Issue Type: Improvement
> Reporter: Grant Ingersoll
> Assignee: Grant Ingersoll
> Priority: Minor
> Fix For: 4.0
>
> Attachments: LUCENE-3615.patch, LUCENE-3615.patch, LUCENE-3615.patch
>
>
> Currently, Test2BTerms has an @Ignore annotation which means that the only
> way to run it as a test is to edit the file.
> There are a couple of options to fix this:
> # Add a main() so it can be invoked via the command line outside of the test
> framework
> # Add some new annotations that mark it as slow or weekly or something like
> that and have the test target ignore @slow (or whatever) by default, but can
> also turn it on.
--
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]
