-
Spike
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
None
-
Quality / Stability / Reliability
-
False
-
-
False
-
None
-
None
-
None
Currently, end-to-end (E2E) Cypress tests for the OpenShift Console are split across multiple repositories:
- QE-owned tests (frontend + backend): openshift/openshift-tests-private (private repo, reports to QE Sippy only)
- Engineering-owned frontend tests: openshift/console (public repo, reports to public Sippy)
This split leads to fragmentation, reduced visibility for QE tests, duplicated efforts, and difficulty in cross-team collaboration.
This spike is intended to investigate and propose a strategy for merging the QE Cypress E2E tests into the openshift/console repository, establishing a unified structure for both frontend and backend tests.
Goals / Deliverables:
- Review the current structure of Cypress tests in both repos (QE and Engineering).
- Identify compatibility or integration challenges (e.g. folder structure, test setup, shared utils).
- Propose a unified folder structure within the openshift/console repo that accommodates Console frontend Cypress tests
- Suggest options for test ownership labeling or folder segregation (e.g. /tests/qe vs /tests/eng)
- Assess Sippy reporting implications (how QE tests can be reported publicly if merged)
- Identify short-term and long-term migration steps (e.g. 1:1 copy vs refactor and consolidate) - in combination with https://issues.redhat.com/browse/CONSOLE-4582
Acceptance Criteria:
- A clear and documented proposal for where QE tests would live in the openshift/console repo
- A recommendation for how to maintain QE vs Eng test boundaries if necessary