According to dnochevn, the scope of this issue is:
1. Create jenkins job(s) to test cmdline installation of CRW 1.2 operator from crw_pr, stage, and production orgs: DONE
2. Add automated UI tests for using the operatorhub UI to install CRW, rather than doing it via oc commands: DONE
- is cloned by
-
CRW-343 Automate testing of installation of CRW 2 on OCP4 and OSD4 using OperatorHub
- Closed
- is related to
-
CRW-64 Automate installation paths testing
- Closed
- relates to
-
CRW-380 publish operator application to quay as part of push-latest-containers-to-quay job
- Closed
-
CRW-221 Implement creation&teardown of OCP 4 cluster for usage in testing jobs.
- Closed
- links to