You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: integration-tests/README.md
+16-13Lines changed: 16 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,26 +26,29 @@ Quick test use cases.
26
26
6. verify domain life cycle(destroy and create) should not any impact on Operator managing the domain and web app load balancing and admin external service
27
27
7. cluster scale up/down using Operator REST endpoint, webapp load balancing should adjust accordingly. (run.sh does scaling by editing the replicas in domain-custom-resource.yaml.)
28
28
8. Operator life cycle(destroy and create) should not impact the running domain
29
+
9. verify liveness probe by killing managed server 1 process 3 times to kick pod auto-restart
30
+
10. shutdown the domain by changing domain serverStartPolicy to NEVER
29
31
30
32
Full test use cases
31
33
32
-
* keep the first domain and operator running
34
+
* keep the first operator running
33
35
* create another domain domain2 in default namespace and verify the domain by doing the checks 2 - 5 listed in quick test
34
-
*destroy domain domain2
36
+
*shutdown and delete domain domain2
35
37
* create another domain domain3 with dynamic cluster using WDT in test1 namespace and verify the domain by doing the checks 2 - 5 listed in quick test
36
38
* verify cluster scaling by doing scale up for domain3 using WLDF scaling
37
-
*destroy domain domain3
39
+
*shutdown and delete domain domain3
38
40
* create another operator operator2 which manages test2 namespace and verify domain1 is not affected
39
-
* create another domain domain4 with Configured cluster using WDT in test2 namespace and verify the domain by doing the checks 2 - 5 listed in quick test
40
-
* verify scaling for domain4 cluster from 2 to 3 servers and back to 2, plus verify no impact on domain1
41
-
* cycle domain1 down and back up, plus verify no impact on domain4
42
-
* create domain5 in the default namespace with serverStartPolicy="ADMIN_ONLY", and verify that only admin server is created. on Jenkins, this domain will also test NFS instead of HOSTPATH PV storage
43
-
* create domain6 in the default namespace with pvReclaimPolicy="Recycle", and verify that the PV is deleted once the domain and PVC are deleted
44
-
* test managed server 1 pod auto-restart in domain1
45
-
* destroy domain1
46
-
* test that create domain fails when its pv is already populated by a shutdown domain
47
-
* create another domain domain7 with APACHE load balancer and access admin console via LB port.
48
-
* create another domain domain8 with mostly default values from sample domain inputs, mainly exposeAdminT3Channel and exposeAdminNodePort which are false by default and verify domain startup and cluster scaling using operator rest endpoint works.
41
+
* create another domain domain4 with dynamic cluster in default namespace and domain domain5 with Configured cluster using WDT in test2 namespace and verify the domain by doing the checks 2 - 5 listed in quick test
42
+
* verify scaling for domain5 cluster from 2 to 3 servers and back to 2, plus verify no impact on domain4
43
+
* cycle domain4 down and back up, plus verify no impact on domain5
44
+
* shutdown and delete both domain4 and domain5
45
+
* create domain6 in the default namespace with serverStartPolicy="ADMIN_ONLY", and verify that only admin server is created. on Jenkins, this domain will also test NFS instead of HOSTPATH PV storage
46
+
* shutdown and delete domain6
47
+
* create domain7 in the default namespace with pvReclaimPolicy="Recycle", and verify that the PV is deleted once the domain and PVC are deleted
48
+
* shutdown and delete domain7
49
+
* create domain domain8 and test that create domain fails when its pv is already populated by a shutdown domain
50
+
* create another domain domain9 with APACHE load balancer and access admin console via LB port. shutdown domain.
51
+
* create another domain domain10 with mostly default values from sample domain inputs, mainly exposeAdminT3Channel and exposeAdminNodePort which are false by default and verify domain startup and cluster scaling using operator rest endpoint works.
0 commit comments