Integration tests should be able to run remotely

[cblackburn]

Some integration tests under both OmeroPy and OmeroJava write files direct to disk. This means the tests fail if run against a remote server. The obvious candidates are

components/tools/OmeroPy/test/integration/test_bfpixelsstoreexternal.py
components/tools/OmeroPy/test/integration/test_bfpixelsstoreinternal.py
components/tools/OmeroJava/test/integration/BfPixelBufferTest.java
components/tools/OmeroJava/test/integration/ExporterTest.java

but there may be others. The two Python cases could be deprecated as part of #11433 as the tests appear to be fully covered in the Java case.

[bpindelski]

The BfPixelBufferTest class might not be trivial to fix. It is indeed possible to remove the new File() code path and upload test files to a remote server using the service factory, but ultimately we end up calling the BfPixelBuffer ctor with a file name and the class is oblivious to any remote connections - it expects the file to be present locally. Maybe BfPixelsBufferTest should really be a type-of-unit test in omero-romio?

[jamoore]

It would require a short review, but if all the tests are solely testing APIs that work in byte[] then there's likely little reason to have remoting in the loop, since we're quite confident that that's not going to go wrong. In which case, either a romio unit test or an internal server integration test would be possible.

[bpindelski]

Josh: An initial (and probably final) fix is in ​https://github.com/bpindelski/openmicroscopy/tree/11480-remoting. I've ran the "integration" target of OmeroJava against a second laptop that was hosting the server instance on a different IP. All tests run fine. I no-one can come up with other corner cases, I'd consider this fixed and open a PR from my branch.

[bpindelski]

Commit opened ​https://github.com/openmicroscopy/openmicroscopy/pull/1594. Closing.