You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Tim Allison (JIRA)" <ji...@apache.org> on 2016/02/04 16:54:39 UTC

[jira] [Resolved] (TIKA-1851) Tika 2.0 - Move test resources from core to test-resources

     [ https://issues.apache.org/jira/browse/TIKA-1851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tim Allison resolved TIKA-1851.
-------------------------------
    Resolution: Invalid

Moved shared test resources to test-resources and did some other very small test clean ups.

One oddity that I'm not sure how to handle or if it is a problem is that tika-test-resources now has junit in full scope (not just test).  My thinking is that all other modules will use tika-test-resources in test scope only so this won't be a problem. If there's a cleaner way of handling this, please let me know.

Had to duplicate a small bit of code from AbstractTikaConfigTest in tika-core to avoid circular dependency, but now we have clean(er) separation of tika-core and tika-test-resources.  My goal was to get to something akin to Lucene's lucene-test-framework.

After working through our unit tests across a variety of parsers recently, I see a large opportunity to refactor many tests and make more use of TikaTest functionality...that's for another ticket.

> Tika 2.0 - Move test resources from core to test-resources
> ----------------------------------------------------------
>
>                 Key: TIKA-1851
>                 URL: https://issues.apache.org/jira/browse/TIKA-1851
>             Project: Tika
>          Issue Type: Sub-task
>            Reporter: Tim Allison
>            Assignee: Tim Allison
>            Priority: Trivial
>             Fix For: 2.0
>
>
> Let's try to move resources that are used for testing to the test-resources module if possible: MockParser, DummyParser, TikaTest and the unit tests for MockParser.  That should also allow us to drop the test-jar goal in tika-core.  Anything else?
> Haven't actually tried this yet; there may be surprises.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)