For the ES backend it'll be very helpful to be able to run (most of) the tests from the "orm" module against the ES backend, too.

The main obstacle atm. is that the test infrastructure tries to resolve the "target" directory based on test classes. This will fail in the scenario described above, as a test from "orm" will be obtained though the dependency JAR and not from the "target" folder of the ES module.