We should create jobs running different installation paths (with/without provided database, with/without provided keycloak, ...) on different target infrastructures.
This jobs should install CRW and then do basic verification of the product
- check resources deployed on openshift
- check config map values
- check installation log for errors
- check basic functionality of product (start workspsace, ...?)
- anything else?
DoD in this issue: Have 3 jobs running against OCP 3.11. One with TLS, one without, one with OAuth support. Other configurations would be implemented in followup issues.
- is related to
-
CRW-234 Create E2E tests to check log into CRW using OpenShift oAuth
- Closed
- relates to
-
CRW-208 Automate testing of offline installation flow
- Closed
-
CRW-209 Setup repo to store resources for installation path tests on CRW Jenkins CI
- Closed
-
CRW-212 Create job for check upgrade CRW form 1.0.1 to 1.1.0 version
- Closed
-
CRW-216 Create job for check installation CRW with default 'deploy.sh' options
- Closed
-
CRW-217 Jobs for CRW installation with provided database and keycloak
- Closed
-
CRW-220 Automate testing of Codeready installation behind proxy
- Closed
-
CRW-223 Automate testing of installation of CRW on OCP4 and OSD4 using OperatorHub
- Closed
-
CRW-241 Create job for check upgrade CRW from 1.1 to 1.2 version
- Closed
-
CRW-343 Automate testing of installation of CRW 2 on OCP4 and OSD4 using OperatorHub
- Closed