Legend:
NOT STARTED IN PROGRESS DEFERRED COMPLETED
Carry over tests from H-release
Reference: Pl. see the child pages of Integration Test details for Honolulu for tests deferred to each track.
| S.No | Topic | Description | Dependency | Tester | Status | Remarks |
|---|---|---|---|---|---|---|
| NSMF_15 | Service instantiation (Option 2) - New NSI | NSMF (SO) calls OOF using selectNSSI API for the RAN NSSI selection (in case of external RAN NSSMF) with RAN Slice Profile and RAN sub-net capabilities. OOF provides response with a suitable RAN NSSI exists (that can be reused). | NOT STARTED | |||
| NSMF_16 | Service instantiation (Option 2) - New NSI | NSMF (SO) triggers External RAN NSSMF with modifyNSSI operation via the NSSMF adaptor (it also sends info of NSSI to be reused), and RAN NSSI is updated successfully. RAN EP info is updated in AAI by NSMF Adaptor. | NOT STARTED | |||
| NSMF_17 | Service instantiation (Option 1) - Reuse existing NSI (Regression) | NSMF (SO) triggers OOF for NSI selection (passing Service Profile, NST and sub-net capabilities), resulting in OOF providing details of existing NSI to be reused in the response. | NOT STARTED | Regression as NSMF_18 should be tested | ||
| NSMF_18 | Service instantiation (Option 1) - Reuse existing NSI | NSMF (SO) triggers OOF for obtaining Slice Profiles for the new Service Profile when an existing NSI is reused, and OOF provides the Slice Profiles. | NOT STARTED | A fix was provided in SO (NSMF) (SO-3629) which will officially be available on H-release-MNT. | ||
| NSMF_21 | Service instantiation (Option 2) - Reuse existing NSI | NSMF (SO) triggers OOF for NSI selection (passing Service Profile, NST and sub-net capabilities), resulting in OOF providing existing NSI to be reused in the response. NSMF (SO) triggers OOF for obtaining Slice Profiles for the new Service Profile when an existing NSI is reused, and OOF provides the Slice Profiles. | NOT STARTED | |||
| NSMF_22 | Service instantiation (Option 2) - Reuse existing NSI | NSMF then calls modifyNSSI API towards Core and Transport NSSMFs, and external RAN NSSMF with details of NSI to be reused and the respective Slice Profile | NOT STARTED | |||
| NSMF_27 | Service termination (Option 1/2) | Service termination from CSMF portal (UUI) for Option 1/2. SO (NSMF) triggers OOF to check for NSI termination, OOF returns NSI should not be terminated | NOT STARTED | |||
| NSMF_28 | Service termination (Option 1/2) | SO (NSMF) triggers RAN, Core and TN NSSMF with modifyNSSI API to remove S-NSSAI from the respective NSSIs. Service and Slice profiles and their links are also removed. | NOT STARTED | |||
| NSMF_29 | Service termination (Option 1) | Service termination from CSMF portal (UUI) for Option 1/2. SO (NSMF) triggers OOF to check for NSI termination, OOF returns NSI should be terminated | NOT STARTED | |||
| NSMF_30 | Service termination (Option 1) | SO (NSMF) triggers RAN, Core and TN NSSMF with deallocateNSSI API. NSI is also removed by SO (NSMF). | NOT STARTED | |||
| RAN_14 | Service instantiation (Option 1) - New NSI, reuse RAN NSSI | SO (RAN NSSMF) calls SO (TN NSSMF) for configuring the existing TN FH/MH NSSIs (reuse) with the new S-NSSAI and respective Slice Profiles using modifyNSSI API. | IN PROGRESS | This test case is only partially completed. So, it is deferred to Istanbul | ||
| RAN_15 | Service instantiation (Option 1) - Reuse existing NSI | 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) | Deepika S | IN PROGRESS | This test case is only partially completed. So, it is deferred to Istanbul | |
| RAN_23 | Service termination (Option 1) | SDN-R makes relevant updates to ConfigDB (removal of S-NSSAI and RAN NF Slice Profile, RRM Policy update) | IN PROGRESS | This test case is partially completed (Slice Profile removal is not yet checked). So it is deferred to Istanbul. | ||
| RAN_24 | Service termination (Option 1) | SDN-R sends relevant (netconf) messages to RAN-NFs (CUs, DUs, Near-RT RICs) of S-NSSAI removal, and update of RRM Policy, etc. | IN PROGRESS | This test case is partially completed - there are some minor issues in RAN-Sim. | ||
| RAN_25 | Service termination (Option 1) | SO (RAN NSSMF) triggers SO (TN NSSMF) for updating the TN FH and TN MH NSSIs. Slice Profiles of TN FH and MH NSSIs are also removed. | TN NSSMF | Deepika S | NOT STARTED | TN NSSMF interactions are deferred to Istanbul. |
| RAN_26 | Service termination (Option 1) | 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) | NOT STARTED | |||
| RAN_27 | Service termination (Option 1) | 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 be terminated. | IN PROGRESS | Deferred to Istanbul release. OOF has some problems and can not support Option1 model. Waiting for OOF changes to be tested | ||
| RAN_28 | Service termination (Option 1) | SO (RAN NSSMF) calls OOF to determine if RAN NF NSSI has to be terminated. OOF returns that RAN NF NSSI should be terminated. | IN PROGRESS | Deferred to Istanbul release. OOF has some problems and can not support Option1 model. Waiting for OOF changes to be tested | ||
| RAN_29 | Service termination (Option 1) | 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 | Deferred to Istanbul release. OOF has some problems and can not support Option1 model. Waiting for OOF changes to be tested | ||
| RAN_30 | Service termination (Option 1) | SO (RAN NSSMF) triggers SO (TN NSSMF) with deallocateNSSI API call for deallocation of TN FH and TN MH NSSIs | IN PROGRESS | Deferred to Istanbul release. OOF has some problems and can not support Option1 model. Waiting for OOF changes to be tested | ||
| RAN_31 | Service termination (Option 1) | 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) | Deepika S | IN PROGRESS | Deferred to Istanbul release. OOF has some problems and can not support Option1 model. Waiting for OOF changes to be tested | |
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