Epic Goal

• Establish the process and guidelines for moving tests from openshift-test-private to a public repo that correlates with the code/feature that they tests so that we an run and report all tests for a component/feature together to get a single quality signal 

Why is this important?

• We need to make it easier for release leads, stakeholders, and engineering teams to see the testing status for a component/feature.

Scenarios

1. Understand where new automated component level tests for OCP components will live
2. Understand where new automated product level tests for OCP will live
3. Understand where test definitions will live
4. Understand how tests will get executed
5. Understand how test results will be reported

Acceptance Criteria

• The location for new automated tests is documented for each component/feature
• The organization mechanisms for new automated tests are documented
• Tests results for new tests are reported alongside existing tests.
•  

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>