-
Story
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
False
-
-
False
-
2
-
None
-
None
-
CLOUD Sprint 277, CLOUD Sprint 278
According to design of OpenShift Tests Extensions, QE automation code should be put into component development team's repo, developer and QE can work together in same repo, feature code and automation case can be submitted in same PR.
In this story, I will investigate following items
- How to implement new test extension binary e.g. https://github.com/openshift-eng/openshift-tests-extension/
- initialize test framework
- add new test suites for different level tests
- How to registry binary for payload conmponent.
- How to registry binary for cpms.
- How to run test/suite via test extension binary
Refer to:
https://github.com/openshift/enhancements/pull/1676
- clones
-
OCPCLOUD-3041 Enable OTE for cluster-capi-operator repo
-
- Code Review
-
- is cloned by
-
OCPCLOUD-3043 Enable OTE for ccm repo
-
- To Do
-
- links to