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 2019/10/21 15:27:00 UTC
[jira] [Resolved] (TIKA-2969) Unit test for
TesseractOCRParserTest.java has confusing behavior when Tesseract not on
path
[ https://issues.apache.org/jira/browse/TIKA-2969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tim Allison resolved TIKA-2969.
-------------------------------
Fix Version/s: 1.23
Assignee: Tim Allison
Resolution: Fixed
Thank you, [~epugh]!
> Unit test for TesseractOCRParserTest.java has confusing behavior when Tesseract not on path
> -------------------------------------------------------------------------------------------
>
> Key: TIKA-2969
> URL: https://issues.apache.org/jira/browse/TIKA-2969
> Project: Tika
> Issue Type: Improvement
> Components: ocr
> Affects Versions: 1.22
> Reporter: David Eric Pugh
> Assignee: Tim Allison
> Priority: Minor
> Fix For: 1.23
>
>
> Tesseract isn't installed on my path by default, I have to set the tesseractPath and tessdataPath properties. In trying to sort things out I ran the TesseractOCRParserTest and was shocked that it worked.. It wasn't till i dug in more that I realized that the unit tests check with the canRun() method, and then either don't run, but with no feedback to the user, or there is the assumeTrue() assert, which just stops the unit tests.
> This issue is to make this test communicate better for the next person!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)