Legend:
| Status | ||
|---|---|---|
|
Carry over tests from H-release
Reference: Pl. see the child pages of Integration Test details for Honolulu for tests deferred to each track.
...
| Status | ||
|---|---|---|
|
...
| Status | ||
|---|---|---|
|
...
| Status | ||
|---|---|---|
|
...
| Status | ||
|---|---|---|
|
...
Service instantiation (Option 2) - Reuse existing NSI
...
| Status | ||
|---|---|---|
|
...
Service instantiation (Option 2) - Reuse existing NSI
...
| Status | ||
|---|---|---|
|
...
| Status | ||
|---|---|---|
|
...
| Status | ||
|---|---|---|
|
...
| Status | ||
|---|---|---|
|
...
| Status | ||
|---|---|---|
|
...
...
IN PROGRESS
...
When triggered by NSSMF Adaptor with modifyNSSI for reusing an existing NSI, SO (RAN NSSMF) triggers OOF for obtaining the Slice Profiles of RAN NF, TN FH and TN MH subnets for updating the respective NSSIs. Slice Profile details are then updated in AAI.
(Remaining flows are similar to test cases RAN_11 to RAN_14)
...
IN PROGRESS
...
...
IN PROGRESS
...
...
IN PROGRESS
...
| Status | ||
|---|---|---|
|
...
When triggered by NSSMF Adaptor with deallocateNSSI API, SO (RAN NSSMF) calls OOF to determine if RAN NSSI has to be terminated. OOF returns RAN NSSI should not be terminated. (Remaining steps are the same as in test cases RAN_22 to RAN_25)
...
...
| Status | ||
|---|---|---|
|
...
...
IN PROGRESS
...
Deferred to Istanbul release. OOF has some problems and can not support Option1 model. Waiting for OOF changes to be tested
...
...
IN PROGRESS
...
SO (RAN NSSMF) triggers SDN-R for removing the S-NSSAI in the RAN NFs. Slice Profile of RAN NF NSSI and RAN NF NSSI are also removed.
(SDN-R actions are covered in test cases RAN_23 and RAN_24)
...
...
IN PROGRESS
...
...
IN PROGRESS
...
When OOF returns that RAN NSSI should be terminated, SO (RAN NSSMF) calls OOF to determine if RAN NF NSSI has to be terminated. OOF returns that RAN NF NSSI should not be terminated.
(RAN NF NSSI update actions are covered by RAN_22 to RAN_24, and TN FH and MH NSSI actions are covered by RAN_30)
...
IN PROGRESS
...
E2E Integration Tests
- Design - Option 1, Option 2
- Instantiation - create new NSI (not-shared, no match with shared, all matching are not-shared, different coverageArea so not matching)
- RAN NSSI - new, Core NSSI - new, TN BH NSSI - new
- RAN NF NSSI - new, ??
- RAN NSSI - reuse, Core NSSI - new, TN BH NSSI - new
- RAN NSSI - new, Core NSSI - reuse, TN BH NSSI - new
- RAN NSSI - new, Core NSSI - new, TN BH NSSI - reuse
- RAN NSSI - reuse, Core NSSI - reuse, TN BH NSSI - new
- RAN NSSI - reuse, Core NSSI - new, TN BH NSSI - reuse
- RAN NSSI - new, Core NSSI - reuse, TN BH NSSI - reuse
- RAN NSSI - reuse, Core NSSI - reuse, TN BH NSSI - reuse (but all 3 are not part of same NSI, otherwise that NSI would have been reused)
- RAN NSSI - new, Core NSSI - new, TN BH NSSI - new
- Instantiation - reuse existing NSI
- Activation
- Deactivation
- Termination
Test Automation
| Children Display |
|---|