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
+11-2Lines changed: 11 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,34 +16,42 @@ Wercker runs only Quick test use cases, Jenkins run both Quick and Full test use
16
16
17
17
Java integration tests cover the below use cases:
18
18
19
-
Quick test use cases.
19
+
Quick test use cases -
20
+
20
21
Operator Configuration - operator1 deployed in weblogic-operator1 namespace and manages domains in defaut and test1 namespaces
21
22
Domain Configuration - Domain on PV using WLST, traefik load balancer
22
23
23
24
Basic Use Cases
25
+
24
26
1. create operator operator1 which manages default and test1 namespaces, verify its deployed successfully, pod created, operator Ready and verify external REST service if configured
25
27
2. create domain domain1 in default namespace and verify the pods, services are created and servers are in Ready
26
28
3. verify admin external service by accessing admin REST endpoint with nodeport in URL
27
29
4. verify admin t3 channel port by exec into the admin pod and deploying webapp using the channel port for WLST
28
30
5. verify web app load balancing by accessing the webapp using loadBalancerWebPort
29
31
30
32
Advanced Use Cases
33
+
31
34
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
32
35
7. cluster scale up/down using Operator REST endpoint, webapp load balancing should adjust accordingly.
33
36
8. Operator life cycle(destroy and create) should not impact the running domain
34
37
35
38
Also the below use cases are covered for Quick test
39
+
36
40
9. verify liveness probe by killing managed server 1 process 3 times to kick pod auto-restart
37
41
10. shutdown the domain by changing domain serverStartPolicy to NEVER
38
42
39
-
Full test use cases
43
+
Full test use cases -
44
+
45
+
```
40
46
Operator Configuration - operator2 deployed in weblogic-operator2 namespace and manages domains test2 namespace
41
47
Domain Configuration - Domain on PV using WDT, Domain with serverStartPolicy ADMIN_ONLY,
42
48
Domain with auto and custom situational configuration, Two domains managed by two operators,
43
49
Domain with Recycle weblogicDomainStorageReclaimPolicy, Domain with default sample values
50
+
```
44
51
45
52
Basic Use Cases described above are verified in all the domain configurations. Also the below use cases are covered:
46
53
54
+
```
47
55
Domain on PV using WDT - WLDF scaling
48
56
Domain with ADMIN_ONLY - making sure only admin server is started and managed servers are not started.
49
57
Shutdown domain by deleting domain CRD. Create domain on existing PV dir, pv is already populated by a shutdown domain.
@@ -57,6 +65,7 @@ Domain with Recycle weblogicDomainStorageReclaimPolicy - create domain with pvRe
57
65
once the domain and PVC are deleted
58
66
Domain with default sample values - create domain using mostly default values for inputs
0 commit comments