Eclipse junit test runner can't run integration tests.

[GoogleCodeExporter]

Currently trying to run the integration tests with Eclipse fails. I've never 
got anything that writes to the filesystem to work in Eclipse. This makes test 
results harder to navigate.

One standard answer is "Aha, you shouldn't write to the filesystem in tests 
anyway!" To some extent we could go in this direction by creating the Lucene 
indexes separately and checking them in as testdata. Still we do need to test 
some I/O to a filesystem or a mock filesystem because this is how the 
integration between building and searching indexes works in practice.

Original issue reported on code.google.com by widd...@google.com on 28 Aug 2011 at 1:46

[GoogleCodeExporter]

Original comment by widd...@google.com on 28 Aug 2011 at 1:46

• Changed title: Eclipse junit test runner can't run integration tests.

[GoogleCodeExporter]

It is possible and quite easy to run these tests in Eclipse. You need to set 
some active directory parameters accordingly, and if the tests fail they 
currently leave the filesystem in a "started" state that will cause subsequent 
test runs to fail. 

Original comment by dwidd...@gmail.com on 1 Apr 2013 at 11:27

• Changed state: Started