Nikola Koevski added a comment - 03/Mar/20 9:22 AM - edited Status update: Support multiple versions of a database type - FINISHED Use in JUnit 3 + JUnit 4 Porting of JUnit 3 base classes (PluggableProcessEngineTestCase, ResourceProcessEngineTestCase, CmmnProcessEngineTestCase) is FINISHED (and works in most cases). All the JUnit3 tests now use a single Test class (PluggableProcessEngineTest). When a Process Engine is built directly in the test from a configuration file, the tests were failing since Testcontainers wasn't hooking into the build process. I have created a ProcessEngineProvider wrapper class to substitute the ProcessEngineConfiguration#createProcessEngineConfigurationFromResource method call and enable Testcontainers to be hook into the build process. The ProcessEnginesTest looks for camunda.cfg.xml files directly on the classpath. I worked around this by providing a TestClassloader that limits the classpath access to a given package. I also restricted the test to the H2 database since it's testing a functionality independent of the database type. Currently, there are no test failures when running individual test packages, but there are still some when running the complete test suite. I plan to try the following approach: Migrate all the tests to JUnit4 Debug the failing tests. I also need to confirm that the TC integration works on Eclips. The plan is to set up Eclipse myself and test it there. To test operation with a remote Docker environment, I plan to use a Raspberry Pi and configure the Docker daemon to accept remote connections. This will provide an idea on how it can be done.