SO subcomponents MSOCoreBPMN and mso-vnf-adapter JUnit tests have (apparently unintended?) dependencies that require their execution in specific order.

• For MSOCoreBPMN test case PropertyConfigurationTest must be executed before HealthCheckHandlerTest because of volatile storing of the system property "mso.config.path" in PropertyConfiguration.startUp() (the system property is not set in HealthCheckHandlerTest but the startUp() method is nevertheless called)

• For mso-vnf-adapter the following test cases require CloudConfig to be initialized:  VolumeAdapterRestExceptionTest.createVNFVolumesClassFormatError

  VolumeAdapterRestExceptionTest.queryVNFVolumesNullPointerException

  VnfAdapterRestExceptionTest.createVfModuleClassFormatError

  VnfAdapterRestExceptionTest.queryVfModuleNullPointerException

  VnfAdapterRestExceptionTest.updateVfModuleClassFormatError   

  MsoVnfCloudifyAdapterImplTest.queryVnfNullPointerExceptionTest

…but the initialization is actually done only in QueryTest and MsoVnfAdapterImplTest. If any of the above 7 test cases are executed before the latter two, they fail to IllegalStateException "No valid CloudConfig is loaded".