Uploaded image for project: 'Operator Runtime'
  1. Operator Runtime
  2. OPRUN-3019

Origin e2e's for OLMv1 and Platform Operators

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • Origin e2e's for OLMv1 and Platform Operators
    • 6
    • False
    • None
    • False
    • Not Selected
    • To Do
    • 67% To Do, 17% In Progress, 17% Done

      Epic Goal

      • Add e2e tests for OLMv1 and Platform Operators functionality in the origin test suite

      Why is this important?

      Without these tests, we run the risk of breaking to OCP when we merge breaking changes to our components downstream. For example, if we change how catalogd serves catalog metadata, it's own e2e's would pass because we can change e2e tests at the same time that we change the functionality.

      However, operator-controller depends on catalogd, so we need a way to ensure that a catalogd change does not break operator-controller's usage of it. This is where origin e2e tests come in.

      Scenarios

      1. Create a Catalog object and verify it unpacks/syncs successfully
      2. Create an Operator object (referencing a package in the catalog created in step 2), and verify it installs successfully.
      3. Create a PlatformOperator object and verify it installs successfully

      Acceptance Criteria

      • All e2e tests pass successfully
      • Attempting to merge a change in the downstream rukpak repo that causes platform-operators to break results in an origin e2e failure
      • Attempting to merge a change in the downstream rukpak repo that causes operator-controller to break results in an origin e2e failure
      • Attempting to merge a change in the downstream catalogd repo that causes operator-controller to break results in an origin e2e failure.

      Previous Work (Optional):

      1. https://issues.redhat.com/browse/OPECO-2821
      2. https://issues.redhat.com/browse/OPRUN-2934
      3. https://issues.redhat.com/browse/OPRUN-2935
      4. https://issues.redhat.com/browse/OPRUN-2933

      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>

              agreene1991 Alexander Greene (Inactive)
              jlanford@redhat.com Joe Lanford
              Jian Zhang Jian Zhang
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: