Epic Goal

• To track the work on improving the test suite in current installer pre-submit testing
• mini-permission:
  AWS: This was already done in https://github.com/openshift/release/pull/58833
  GCP: ...
  Azure: ...
• private cluster:
  AWS:
  GCP:
  Azure:

Why is this important?

• This can help us catch regression issues as soon as possible to improve product quality and stability. 

Scenarios

1. refer to issues in this epics for more details.

Acceptance Criteria

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

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>