We need  to clarify some questions about test process for WTO and DWO projects:
1) WTO: We have earlier implemented UI/e2e test for WTO here:https://github.com/openshift/console/tree/master/frontend/packages/dev-console/integration-tests/features/web-terminal
The user stories are described in user-readable files. We need to clarify: Is it actually for us or do we need to change/adapt it?
If it stultified us we need to fix and finish the web-terminal-devuser.feature and web-terminal-adminuser.feature. Because currently, it does not work. It would be nice to think about how we can use it in the automated process.
Also, we have the "old" test plan for WTO: https://issues.redhat.com/browse/WTO-36
And we need to decide if is it actual or not. In case of actuality - we need to make a decision about automating it and how it will work with the UI tests
2) DWO: For this project, we created the e2e test earlier: https://github.com/devfile/devworkspace-operator/tree/main/test/e2e. I want to clarify if is it actual or not. If actual - how do we apply it in automating processes?
Also, we have a test plan: https://gist.github.com/amisevsk/1bdfa7b063e4c1a0cb420314a9c14ae6
And we need to think about automation and how we should run this testcases and e2e testcases. Or do we need to combine it together?
And last question: we created more than 1 year ago CPaaS gating job:https://main-jenkins-csb-crwqe.apps.ocp-c1.prod.psi.redhat.com/job/WTO/job/wto-cpaas-gating/  The main idea was listen to the release event in RH UMB. If we catch the release Job has been finished - we set up the clear cluster and run a smoke test with the just-released image. And send back the test results into the release job. We need to clarify the actuality of this part for us.