Partition service integration tests

Partition integration tests are refactored so that the business logic for integration tests resides in the partition-test-core module and provider specific logic and execution steps reside in provider module. To run the integration tests, the core module is built first and then the provider module is executed. Please read further to know more details.

Dependencies needed to run the integration tests

• JDK8

• Maven

• Values for the following environment variables in Config.java (in partition-test-core module)

   ENVIRONMENT ('local' for local testing or 'dev' for dev testing) 
   PARTITION_BASE_URL (service base URL, required only if running integration tests against a cloud endpoint)
   CLIENT_TENANT (name of the client partition, required only if running integration tests against a cloud endpoint) (e.g. 'common')
   MY_TENANT(name of the OSDU partition, required only if running integration tests against a cloud endpoint) (e.g. 'opendes')
  

  Above variables should be configured in the release pipeline to run integration tests. You should also replace them with proper values if you wish to run tests locally.