Epic Goal

• Migrate OLMv1's origin-based tests to its downstream operator-framework-operator-controller repo

Why is this important?

• Changing tests in origin is often time-consuming because origin's pre-merge test suite is very large and often requires multiple CI runs. Even if the failures are unrelated to our change, they require investigation and overrides.
  • This may not be fully avoidable. We may need to add more cluster variants to our component payload tests to get the same coverage we currently get in origin.
• On some occasions, there is a need to change origin and our component somewhat atomically to achieve a particular goal. By locating our origin test code with the component we:
  • Avoid the careful dance that is often required which is often:
    • Make a change to the component that will continue to pass existing origin tests
    • Change origin tests to use the new component change
    • Remove dead/unnecessary code from the component now that origin tests are using the chage
  • Decrease 3 PRs down to 1 PR
  • Decrease CI wait states
  • Decrease CI costs

Supporting materials

1. Integration guide: https://docs.google.com/document/d/1cFZj9QdzW8hbHc3H0Nce-2xrJMtpDJrwAse9H7hLiWk/edit?tab=t.0#heading=h.66y4kqbj468a
2. Enhancement Proposal: https://github.com/openshift/enhancements/blob/master/enhancements/testing/openshift-tests-extension.md

Acceptance Criteria

• All existing OLMv1 origin tests are provided by a test extension binary from the operator-framework-operator-controller repo.
• (Ideally) no point at which are tests are disabled as we transition
• (Ideally) no impact to component readiness measurements as we transition

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. …

Open questions::

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>