You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Robert Muir (Created) (JIRA)" <ji...@apache.org> on 2012/04/12 07:00:29 UTC

[jira] [Created] (LUCENE-3974) Add infra for "integration-test" modules.

Add infra for "integration-test" modules.
-----------------------------------------

                 Key: LUCENE-3974
                 URL: https://issues.apache.org/jira/browse/LUCENE-3974
             Project: Lucene - Java
          Issue Type: Test
          Components: general/build
            Reporter: Robert Muir


LUCENE-3969 is the first use case that really motivated me to open this:

Here we are building random Analysis chains from all the Tokenizers, TokenFilters, 
CharFilters, etc that we can possibly find, and kicking them around to find bugs.

But we only do this in the analyzers-common module. Really I want to combine
all the analysis components across common, phonetic, kuromoji, uima, icu, etc to 
create more interesting chains and increase test coverage.

So I think along with having a modular architecture, we have some responsibility
to test different modules combined together, as sometimes we find bugs like
LUCENE-3920 that no unit test will ever discover.

Can/Should we create some sort of test module that depends on *every lucene module* and
is a free-for-all for crazy integration tests?


--
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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org