At the moment the testing process that is instantiated by each team can be improved. What we need is a CICD pipeline that is effective and testing frameworks and practices that cover also integration testing. See an ongoing discussion in https://confluence.skatelescope.org/x/7Up0B.

This enabler aims at exploring technical feasibility of using Contract testing for API testing, enhancing reporting test executions (for example using http://allure.qatools.ru/ ) , and a lean CICD pipeline.

I envision this to be done as one or more timeboxed spikes.

Acceptance criteria

1. we have understood how Pact could be used by a pair of teams that are involved in developing components within the MVP, like OET and TMC, or TMC and SDP.
2. a prototype of a streamlined pipeline has been implemented and tried on at least two components within the MVP (like OET and TMC, or TMC and SDP). The prototype pipeline should be general enough to cover the MVP.
3. The pipeline should cover all the stages mentioned in https://confluence.skatelescope.org/x/7Up0B. 
4. Most stages of the pipeline should produce machine readable test reports (coverage, xunit-reports for test execution, allure reports).