Research and propose a centralized, versioned, and accessible solution for tracking integration (both ephemeral and stage) test plans written across separate codebases (e.g. IQE).

There are, and there will be more, valuable integration tests that are written in IQE, thus a completely different code base compared to the one we are using to keep track of component test plan.

We want to have a convenient place to keep track service (both internal and external) integration test plans.

The test plans should be easily accessible (publicly) and versioned. Moreover they should not be tied, even with their position, to a specific service.

The pointer to the location of the test implementation should be easily understandable (maybe also from the test ID).

Acceptance criteria:

• different solutions are proposed to the team
• a collective decision is made
• Add future proofness for when we split the repos.
• Bring to Team Thunder at the SWATCH Testing Strategy Working Group Meeting for cross collab understanding and future awareness
• Create a card to do a pilot for integration tests.
  • Start from a service that already has IQE ephemeral tests (like swatch-utilization does).