[
https://issues.apache.org/jira/browse/LUCENE-2768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12932957#action_12932957
]
Robert Muir commented on LUCENE-2768:
-------------------------------------
ok, i have two potential solutions, and no particular preference as to which we
do:
# we upgrade our Junit from 4.7 to 4.8 and use the Category support.
in this case you would use @IncludeCategory(Nightly.class) to annotate your
test.
http://kentbeck.github.com/junit/doc/ReleaseNotes4.8.html
# we add our own annotation (e.g. @Nightly) and use that.
in either case we hack our runner to respect it, so its the same amount of work
(junit 4.8 won't actually save us anything since we won't use its
@RunWith(Categories.class), but our own runner), its just about syntax and
possibly if we care about consistency with junit or envision other optional
categories beyond "nightly".
> add infrastructure for longer running nightly test cases
> --------------------------------------------------------
>
> Key: LUCENE-2768
> URL: https://issues.apache.org/jira/browse/LUCENE-2768
> Project: Lucene - Java
> Issue Type: Improvement
> Reporter: Michael McCandless
> Fix For: 3.1, 4.0
>
> Attachments: LUCENE-2768.patch
>
>
> I'm spinning this out of LUCENE-2762...
> The patch there adds initial infrastructure for tests to pull documents from
> a line file, and adds a longish running test case using that line file to
> test NRT.
> I'd like to see some tests run on more substantial indices based on real
> data... so this is just a start.
--
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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
