...
WindRiver Integration LAB:
Test Cases:
No. | Name | Involved components | Pre-conditions | Test Steps | Expect Result | Test Result | Status(Update every week.) |
1 | Successful design of NST, NSST | SDC | 1.The 3rd party NSST package is ready(CN only). | 1.Login to SDC as designer. 2.Create Service template, Select 'NSST' as Category, and design the NSST with 3rd party NSST as artifacts. define the capabilities of the NSST. 3.Create Service Template select 'NST'as Category,and design the NST. composed by NSST(service-proxy). define the capabilities of the NST. 3. Do the test, approve, distribute operation. | 1.The NST and NSST have been distribute successfully to SO,A&AI, SDC distribution monitor shows ok. Developers can further check the dbs. a.In A&AI model nodes , the template information is there. b.In SO catalog db. the models have been distributed. | NOT YET TESTED | |
2 | Successful design of CST ,Service Profile Template | SDC | 1.NST,NSST designed. | 1.Login to SDC as designer. 2.Create the NSTAR(allotted resource for NST) 2.Create Service template, Select 'Service Profile' as Category, composed by the NSTAR. define the parameters of the Service Profile Template. 3.Create Service Template select 'CST'as Category,and design the NST. composed by ServiceProfile(service-proxy). define the capabilities of the CST. 3. Do the test, approve, distribute operation. | 1.The ServiceProfile Template and CST have been distribute successfully to SO,A&AI, SDC distribution monitor shows ok. Developers can further check the dbs. a.In A&AI model nodes , the template information is there. b.In SO catalog db. the models have been distributed. | NOT YET TESTED | |
3 | Service instantiation |
- new NSI/new NSSI to be instantiated | UUI, SO, OOF, AAI | 1.NSST, NST, ServiceProfile Template, CST designed in SDC and distributed successful. 2.NSSMF information registered to ESR. |
|
NOT YET TESTED
Service instantiation via CSMF portal resulting in NSI selection without any override by operator via NSMF portal - existing NSI to be selected
| 1.In "5G Slicing Management"/"Communication Service " the slice service is there , and the status is "deactivated". 2.In "5G Slicing Management"/"Slicing Task management" Page,the task changed to "completed". 3.In "5G Slicing Management"/"Slicing Resource Mangement/Slicing Business Management" the service is there. 4.In "5G Slicing Management"/"Slicing Resource Mangement/Slicing Instance Management" the new NSI is there. view detail you can find the service attached to the NSI. 5.In "5G Slicing Management"/"Slicing Resource Mangement/Slicing Subnet Instance Management" the new NSSI is there. view detail you can find the NSSI is connected to the NSI. | NOT YET TESTED | |
4 | Service instantiation - existing NSI to be selected |
UUI, SO, OOF, AAI | NOT YET TESTED |
5 | Service instantiation |
- new NSI/shared NSSI to be instantiated | UUI, SO, OOF, AAI | NOT YET TESTED | |||||
7 | Service activation from CSMF portal – resulting in slice service activation | UUI, SO, AAI | NOT YET TESTED | ||||
8 | Service de-activation from CSMF portal – resulting in slice service deactivation | UUI, SO, AAI | NOT YET TESTED | ||||
9 | Service termination (remove service profile/slice profile from NSI/NSSI) | UUI, SO, AAI | NOT YET TESTED | ||||
10 | Service instantiation request via ExtAPI (using postman) - resulting in new NSI to be instantiated | ExtAPI, SO, OOF, AAI | NOT YET TESTED | ||||
11 | Service instantiation request via ExtAPI (using postman) - resulting in reuse of existing NSI | ExtAPI, SO, OOF, AAI | NOT YET TESTED |