Epic Goal

• The goal of this epic is to stabilise the failing or inconsistent scenarios in the RH prow CI currently running on s390x architecture --> This will be taken care of as. part of https://issues.redhat.com/browse/MULTIARCH-5822 
• For QE - We must also reduce any irrelevant test scenarios and streamline the test suite for release
• The regression cycle period to be reduced to. 1.5 - 2 weeks from the current 3 weeks.

Why is this important?

• The RH CI should be a comprehensive indication for any release blockers for the ocp version release, by streamlining the test cases and stabilising the running scenarios we need to avoid false failures and be cognisant of any blockers early in the release cycle.
• Overall efforts in QE should be streamlined by identfifying the test cases for duplication , irrelevance and see where is the possibility to combine the cases to cover in single execution.

Scenarios
1. …

Acceptance Criteria

• All new test scenarios to be added and tested on the CI , as passing. 
• All test scenarios should not be failing inconsistently showing a false positive outcome.
• All scenarios discarded should not be running for the CI or the periodicity to be drastically reduced.
• Test cases covered as part of QE are streamlined with priorities defined and no duplication present.

Dependencies (internal and external)
1. Dependency on the IBM QE team to finalize the test cases and priorities

Risks:
Do not see any risk for this item. 

Previous Work (Optional):
1. The scenarios that are needed have been discussed with RH, IBMZ and Power and a consensus on the required / not required scenarios has been achieved.

Open questions::
1. …

Done Checklist

• CI - For new features (non-enablement), existing Multi-Arch CI jobs are not broken by the Epic
• Release Enablement: <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR orf GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - If the Epic is adding a new stream, downstream build attached to advisory: <link to errata>
• QE - Test plans in Test Plan tracking software (e.g. Polarion, RQM, etc.): <link or reference to the Test Plan>
• QE - Automated tests merged: <link or reference to automated tests>
• QE - QE to verify documentation when testing
• DOC - Downstream documentation merged: <link to meaningful PR>
• All the stories, tasks, sub-tasks and bugs that belong to this epic need to have been completed and indicated by a status of 'Done'.