Epic Goal*

This epic aims at onboarding OTA QE on the openshift test extension framework. The outcome of this epic is QE having tests merged in CVO repository.

Why is this important? (mandatory)

This extends Dev/QE collaboration in testing by using shared tests, shared practices and shared results. This eventually leads us to real agile development. Often times, QE testing and automation development are after Dev work, many stories/tasks were not closed in target sprint because they are awaiting QE tests. 

As a distributed team, OTA Dev/QE have an 8~12 hours gap, enabling QE to write tests early and have Dev review early leads to faster delivery.

While some may question QE tests in o/openshift-tests-private and CI jobs in o/release repositories already have good test coverage, why would we adopt a new framework? Let's do not ignore the fact that Dev/QE tests still have silos. The test cases and test result performance are not well known to both of their counterparts. Having a unified repository for tests eliminates the ambiguous situation of "assuming tests have coverage".

Scenarios (mandatory) 

Provide details for user scenarios including actions to be performed, platform specifications, and user personas.  

1. QE owner review the tests they own, and select the first test that could be written in CVO repository. It's advised to start small, do not be too ambitious on very complicated tests(aka. update-time tests, monitor tests). It's ok to write test that had been automated in o/openshift-tests-private.
2. QE update their Jira tracker and clarify what test they want to develop.
3. QE creates the PR for review, address the comments and have the tests merged.
4. Use the PR as the baseline and start to develop more tests, sharing experience and practices.

Dependencies (internal and external) (mandatory)

Contributing Teams(and contacts) (mandatory) 

• QE

Acceptance Criteria (optional)

• Every OTA QE have their test merged in CVO

Done - Checklist (mandatory)

The following points apply to all epics and are what the OpenShift team believes are the minimum set of criteria that epics should meet for us to consider them potentially shippable. We request that epic owners modify this list to reflect the work to be completed in order to produce something that is potentially shippable.

• Testing in CVO
• Integration of OTE, tests results available on Sippy
• Sharing/Demos about test development
• Other