Mockoon tests to cover different exporters

[KevinMGranger]

This is a tracking issue regarding our use of mocked APIs when testing.

The idea was initially proposed in #270.

• [x] Run integration tests as part of CI (#296)
• [ ] Commit Time Exporters
  • [x] GitHub (mocks added in #281, tests in #296)
  • [ ] GitLab
  • [ ] Azure DevOps
  • [ ] BitBucket
  • [ ] Gitea
  • [ ] Image (#760)
• [ ] Failure Exporter (no issue/PR yet)
• [ ] Deploy Time Exporter (no issue/PR yet)

Further Work

@fmenesesg is looking into kicking off the mock server as part integration tests run via GitHub Actions.

See #296.

[mpryc]

The documentation on how to record session using mockoon should be in place before proceeding with this work.

[mateusoliveira43]

I suggest we do not use Mockoon anymore.

I have been writing integration test in my past tasks, and I believe they are working well. What I have worked on:

• https://github.com/dora-metrics/pelorus/blob/master/exporters/tests/__init__.py#L18-L43
• https://github.com/dora-metrics/pelorus/blob/master/exporters/tests/test_committime_exporter_app.py
• https://github.com/dora-metrics/pelorus/blob/master/exporters/tests/test_failure_exporter_app.py

Limitations:

• currently, they are not run during PRs, but we will fix this https://github.com/dora-metrics/pelorus/issues/838
• they run on the providers' APIs, so they are slower
• for committime (probably deploytime as well) exporter tests, we need to write a mock API of OpenShift, but I believe we can use some python library (like https://pypi.org/project/model-bakery/) to help us do this

What you think?