feature/smoke tests

[baywet]

fixes #2020

[andreaTP]

@baywet let me share a proposal for this PR 🙂

Would it be possible to split it into multiple PRs?
A first one only with the infrastructure needed to perform the tests, and one per language afterward to actually use the infrastructure to perform the IT tests in CI.

I would really like to properly review the infrastructure work, but it's getting a bit "noisy".
Also, by doing it with iterations we can separate the resolution of the issues that we will be found in the process.
wdyt?

[baywet]

@andreaTP Thanks for the suggestion. I'm going to implement most languages myself as part of this PR (this is core work for the GA, I don't think it'd be fair to "delegate" it to the community). The work is still early, I'm exploring things at this point and each test requires a commit to be pushed (as opposed to running things locally). I'm still expecting large changes and splitting things up at this stage would introduce a lot of coordination overhead.

As for the noise, you can ignore the PR as long as it's in draft, and only pay attention to it when it switches to ready for review.

[baywet]

@andreaTP, let me know what you think.
You can see the results here

[andrueastman]

This is really great to bring in and setup.

Just a couple of suggestions. Otherwise, looks good to me.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[andreaTP]

Haven't had time to review, but the output seems really great! 👍 well bone @baywet !!!

[andreaTP]

@baywet checking this a little bit more through, awesome job!
A couple of things for the future:
Do you think we can expand and set up a MockServer so that the Integration tests will actually need to successfully perform a few calls? Or do you expect this step to be defined by each specific language?

The setup looks a bit tricky(as expected ...), do we have any "easy way" to run one of those tests for development purposes? Would a top-level Makefile or a few separate scripts help?

Based on the previous, would running into a pre-configured Docker image(with all of the tools already installed) help in terms of the reproducibility of the setup?

[baywet]

a mock server would be an awesome step forward! I think that if we want to get there we first need to address a lot of the issues that were discovered. Then we'd need to tweak the projects a bit so they make calls, or even generate the calls to make?

As per the docker image, are you thinking of adding all the language dependencies onto a single image definition or about something else?

[andreaTP]

are you thinking of adding all the language dependencies onto a single image definition

Not a fully formed idea unfortunately, I'm only trying to understand how the tests can be easily run during the dev cycle locally (as opposed to "in CI").