Integration tests Refactoring & Reworking

[helkv]

Ticket for the revision of the existing integration test and the development of new integration tests.

Reasons for the refactoring and reworking of the Imeji integration tests:

• The existing integration tests were not executed for a long time
  • some of them were not up to date and did not run any more
• Embedded Elasticsearch, which some tests rely on, is not supported in the new Elasticsearch version any more
• After major changes in Imeji a new testing approach and test setup is needed

Steps for the revision of the integration tests setup:

1. Analysation of the existing integration tests and their structure
2. Handling of the existing integration tests
   1. Deletion of existing tests which are out dated and in a bad condition
   2. Refactoring of existing tests which are in good condition and fit in the new test setup
   3. Continue to use (parts of) existing tests which are in good condition and still run successfully
3. Reimplementation of the Elasticsearch access within the tests
4. Implementation of the new integration tests, on basis of the new Imeji architecture and the new testing approach

[helkv]

Updated integration tests get executed on Jenkins with every imeji commit/build.

[helkv]

Further refactoring & reworking of the integration test.