Note that the full regression test suite takes a long time and some
of the tests are currently broken (outside of the recent text
extraction failures).
https://issues.apache.org/jira/browse/PDFBOX-394
I haven't run the full test suite in a while, but there are some
performance tests and I seem to recall that they were slow. The text
extraction test isnt' bad. It takes about 4 minutes on my system
(including a build and test).
brian
On Mar 17, 2009, at 8:58 AM, Daniel Wilson wrote:
We could either change the Hudson configuration to run "ant
test dist", or include "test" as a dependency to the "dist" target.
I'd prefer the latter option, as that forces more people to run the
tests during normal development.
While getting more people testing is definitely good, newer
developers may
struggle with the junit setup and be turned off if they can't get a
build
without junit working. I know I struggled with the whole java
build process
and junit when I got started on this. I was an experienced
developer, but
not a <b>java</b> developer at the time.
So I would suggest the former option.
Daniel Wilson
On 3/17/09, Jukka Zitting <[email protected]> wrote:
Hi,
On Fri, Mar 13, 2009 at 9:20 PM, Brian Carrier
<[email protected]> wrote:
Can we modify the automated build system to perform the textextract
regression test and report any failures?
Our Hudson build does an "ant dist" whenever changes are committed to
the trunk. We could either change the Hudson configuration to run
"ant
test dist", or include "test" as a dependency to the "dist" target.
I'd prefer the latter option, as that forces more people to run the
tests during normal development.
In any case, the "test" target doesn't seem to make the build fail
even when there are test failures. That should probably also be
changed.
BR,
Jukka Zitting
