Testing strategy for image-builder

[dekiel]

The image-builder application is composed by few components. These components are running in different tools and technology stacks. Application components exposes it's APIs and interact each other. The component and API that is used by component must be compatible. The compatibility must be maintained when any of application component is changed. To maintain compatibility we must test the application changes in a way which will prove components can interact properly.

Image builder components are.

• Image builder golang binary.
• Image builder GitHub action.
• Image builder reusable workflow.
• Image builder oci-image-builder ADO pipeline.

We must define a way how to test each component in insolation, when it is changed and how to test compatibility with components it interacts with.

• [ ] We have testing strategy defined for each application component.
• [ ] Testing strategy must describe how to test component in insolation.
• [ ] Testing strategy must describe how to test component compatibility with components it interacts with.
• [ ] Testing strategy is documented.
• [ ] Each component is tested according to defined testing strategy.