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 cluster-capi-operator.
• How to run test/suite via test extension binary

Refer to:

https://github.com/openshift/enhancements/pull/1676 

https://issues.redhat.com/browse/OCPERT-1 

https://github.com/openshift/machine-api-operator/pull/1338