We have Oozie JUnit test cases above 2000 pieces right now. To run all the JUnit tests before a patch submission is an overkill since these take more than two hours.
As a workaround we can use the dist_test framework that allows for parallel test execution - the load is distributed across possibly hundreds of cloud engine slaves. So the JUnit tests run time will equal to the longest JUnit test run, that is, in the order of 10-ish minutes for the whole test suite across all the Oozie components.
Nevertheless, some test cases that try to read files with relative access (e.g. src/test/resources/oozie-site.xml), or get system properties that are not present on cloud slaves, will certainly fail. This improvement addresses that exact issue by making those tests pass also on the cloud.