"Could not load an entity" error when upgrading module

yes it did change the property

from: jdbc:h2:mem:openmrs;DB_CLOSE_DELAY=30;LOCK_TIMEOUT=10000

to: jdbc:h2:mem:openmrs;DB_CLOSE_DELAY=30;LOCK_TIMEOUT=10000;MVCC=TRUE

this is the code I added to my RadiologyServiceComponentTest as suggested by @darius

	@Override
public Properties getRuntimeProperties() {
	Properties result = super.getRuntimeProperties();
	String url = result.getProperty(Environment.URL);
	if (url.contains("jdbc:h2:") && !url.contains(";MVCC=TRUE")) {
		result.setProperty(Environment.URL, url + ";MVCC=TRUE");
	}
	return result;
}

what happens now is that the RadiologyServiceComponentTest pass if I only run the unit tests of this file alone. before adding the snippet all tests which touch code calling orderService.saveOrder fail (see stacktrace on my first post), so thats better.

But, if I run all tests of my api, I am back where I started, the same tests fail again!

Why does it make a difference if I run the tests of one class and then run tests of all classes. Shouldnt they be independent? Fresh DB gets set up for every unit test?