Epic Goal

• For the Dev Preview delivered with ACM 2.5, e2e testing was not provided. Thus, this epic provides e2e tests and UT check in hub-of-hubs-manager repo for the capabilities delivered in the 2.5 Dev Preview.

Why is this important?

• Automated e2e testing increases the speed in which code can be delivered
• Automated e2e testing increases the quality of the code delivered.
• We do not know if the code is breaking the existing features or not.

Scenarios

1. The automation e2e tests should be triggered when the PR is submitted
   1. the test scenarios include https://docs.google.com/document/d/1a0cX_FzMXQaMM_HyBolXir2ce7XAab-re_KrQE9gp-c/edit

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.

Dependencies (internal and external)

Previous Work (Optional):

Open questions::

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>