Integration tests

[soxofaan]

From #52

We currently only have unit tests (some of which actually go pretty far to do integration test kind of checks against dummy back-ends), but it would be good if there was also a bit of real integration tests against real back-ends

[soxofaan]

Idea to be covered:
merging of collections (#5) could trigger some warnings or even errors (e.g. incompatible metadata from upstream providers). An integration test could check for these warnings/errors

[soxofaan]

#76 added initial reporting tool for collection and process metadata merging issues. This should be integrated in the integration tests

[soxofaan]

To start this task simple:

• create basic pytest based test suite skeleton in top level folder integration-tests, largely based on https://github.com/Open-EO/openeo-geopyspark-integrationtests, but much simpler (just the part to get root URL from an env var).
• some simple tests:
  • simple test to check if https://openeocloud.vito.be/openeo/1.0/ returns with something sensible
  • does /collections look ok?
  • does /processes look ok?

[soxofaan]

just merged initial skeleton of PR #104

next steps:

• Figure out how to do get authenticated connection (without exposing secrets in this repo)
• set up jenkins flow to run this regularly or trigger based (e.g. pre-release check)

[soxofaan]

I've set up basic configs for running integration tests in jenkins (triggered at end of normal openeo-aggregator run)

[soxofaan]

next step of working with authenticated connection is probably best done through:

• support client credentials grant from Connection.authenticate_oidc() openeo-python-client#419

and getting client credentials from Vault (which will be easier than messing around with private repo's)