Goal

Improve the overall quality of the oc-mirror and the confidence level for developers with oc-mirror.

(Non-goal) Not meant to replace QE's full regression testing for all feature flags and edge cases.

Benefit Hypothesis:

Currently, oc-mirror v2 has no integration tests enabled.

The introduction of integration tests would allow for a more comprehensive testing of the features oc-mirror offers. i.e (this is not exhaustive)

• mirror-to-disk
• disk-to-mirror
• mirror-to-mirror
• delete

These tests would reside in a separate repository from oc-mirror and could be triggered to execute from any CICD pipeline (i.e PROW, Konflux, custom) etc.

The thinking here is that once we submit a PR (over and above the unit tests that we have for v2), we execute these integration tests that will execute these flows and validate the relevant artifacts.

The main goal is to improve the overall quality of the oc-mirror and also enable developers with a better confidence level in oc-mirror.

This testing does not replace QE's full regression testing for all feature flags and edge cases.

Success Criteria

• Well-documented testing matrix
• All flows are tested
• Validate artifacts 
  • tar file
  • cluster-resources
  • mapping file
  • output logs and error logs
  • exit codes
  • expected images on remote registry (i.e via curl)
• Integration into PROW
• Integration into Konflux