Epic Goal

Increase developer confidence when making changes to the MCO code base.

Why is this important?

https://docs.google.com/document/d/1GgQ34EromNlxtLbW593QrqFRDvaW44TqzRi33EmzQ0M/edit?tab=t.0

• We have recently lost our dedicated QE resource
• There are some manual tests that we rely on for critical flows in MCO
• Developers have low confidence in upgrades and regression impact for changes and we want to make it easier
• Currently our QE Regression suite is managed in a different repo and run once a train and towards the end of a release to certify an RC , (and z-streams) https://github.com/stolostron/observability_core_automation/blob/main/tests/pkg/tests/results.xml
• We manage e2e CI tests via MCO repo https://github.com/stolostron/multicluster-observability-operator/tree/main/tests/pkg/tests
• There are also manual test cases in polarion that do not have automated tests

Scenarios

https://polarion.engineering.redhat.com/polarion/#/project/RHACM4K?shortcut=favorites%2FTest%20Runs

Acceptance Criteria

• Our highest priority manual e2e tests are automated
• E2e CI and regressions tests are the same and live in one place
• Engineers on the MCO team are able to craft e2e test scenarios locally with minimal environment setup

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 - Doc issue opened with a completed template. Separate doc issue
  opened for any deprecation, removal, or any current known
  issue/troubleshooting removal from the doc, if applicable.