Epic Goal

• Improve the code quality of the foundation components

Why is this important?

• Red Hat is moving into cloud services and we need to ensure that updates are being delivery with quality without introducing bugs or regressions into our services
• Bugs or regression can lead to service downtime which will impact service SLOs and RH / Customer SLAs

Scenarios

1. Work out use case list of foundation repos and find out missing end-to-end/canary test cases;
2. Add missing end-to-end test cases of foundation repos;
3. Add necessary canary test cases to cover the major foundation features;

Acceptance Criteria

• All scenarios are met

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. See previous work from 2.7:  https://docs.google.com/document/d/19gzio0qfnu_JYlriUMK_Da5CCkVmGFOQXAlio_q3NOU/edit 

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>

ACM Epic Done Checklist

See presentation and details.

Update with "Y" if Epic meets the requirement, "N" if it does not,  or "N/A" if not applicable.

• _ FIPS Readiness: N/A
• _ Works in Disconnected: N/A
• _ Global Proxy Support: N/A
• _ Installable to Infrastructure Nodes: N/A
• _ No impacts to Performance and Scalability: N/A
• _ Backup and Restorable: N/A