Functional Test Cases

Test Environment:

CMCC Integration LAB:

WindRiver Integration LAB:

Test Cases:

No.	Name	Pre-conditions	Test Steps	Expect Result	Test Result	Status(Update every week.)
1	Successful design of NST, NSST	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.	COMPLETED
2	Successful design of CST ,Service Profile Template	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.	CCOMPLETEDOMPLETED
3	Service instantiation - new NSI/new NSSI to be instantiated	1.NSST, NST, ServiceProfile Template, CST designed in SDC and distributed successful. 2.NSSMF information registered to ESR.	Login to UUI portal , and visit the "5G Slicing Management"/"Communication Service " Page. Create a new Communication Service Visit "5G Slicing Management"/"Slicing Task management" Page. Find the task for the network slice, click "Process Task" to deal with it. User check the orchestration results,and fill the script Name for every domain. Click OK to confirm the processing.	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 Management/Slicing Business Management" the service is there. 4.In "5G Slicing Management"/"Slicing Resource Management/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 Management/Slicing Subnet Instance Management" the new NSSI is there. view detail you can find the NSSI is connected to the NSI.	IN PROGRESS	5.11:Because OOF
4	Service instantiation - existing NSI to be selected	1.NSST, NST, ServiceProfile Template, CST designed in SDC and distributed successful. 2.NSSMF information registered to ESR. 3.there is new NSI and NSSI already support the service. 4.OOF policy set so that the shared NSI can be returned.	Login to UUI portal , and visit the "5G Slicing Management"/"Communication Service " Page. Create a new Communication Service Visit "5G Slicing Management"/"Slicing Task management" Page. Find the task for the network slice, click "Process Task" to deal with it. User check the orchestration results,, and fill the script Name for every domain. Click OK to confirm the processing.	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 Management/Slicing Business Management" the service is there. 4.In "5G Slicing Management"/"Slicing Resource Management/Slicing Instance Management" the shared NSI is there. view detail you can find the new service attached to the NSI.	NOT YET TESTED
5	Service instantiation - new NSI/shared NSSI to be instantiated	1.NSST, NST, ServiceProfile Template, CST designed in SDC and distributed successful. 2.NSSMF information registered to ESR. 3.there is new NSI and NSSI already support the service. 4.OOF policy set so that the new NSI/shared NSSI can be returned.	Login to UUI portal , and visit the "5G Slicing Management"/"Communication Service " Page. Create a new Communication Service Visit "5G Slicing Management"/"Slicing Task management" Page. Find the task for the network slice, click "Process Task" to deal with it. User check the orchestration results,, and fill the script Name for every domain. Click OK to confirm the processing.	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 Management/Slicing Business Management" the service is there. 4.In "5G Slicing Management"/"Slicing Resource Management/Slicing Instance Management" the new NSI is there. view detail you can find the new service attached to the NSI. and the shared NSSI is used by the NSI	DEFERRED	This scenario is deferred to Guilin release, as we have only 1 sub-net (core) in Frankfurt release, so it is not useful to cover this scenario now.
6	Service activation from CSMF portal – resulting in slice service activation	1.NSST, NST, ServiceProfile Template, CST designed in SDC and distributed successful. 2.NSSMF information registered to ESR. 3. There is one slice service that is deactivated.	Login to UUI portal , and visit the "5G Slicing Management"/"Communication Service " Page. Select the Communication Service Click "Activate"	1.In "5G Slicing Management"/"Communication Service " the slice service is there , and the status changed to "activated".	IN PROGRESS	0511: NSMF Adapter return 404, Janani is checking this issue.
7	Service de-activation from CSMF portal – resulting in slice service deactivation	1.NSST, NST, ServiceProfile Template, CST designed in SDC and distributed successful. 2.NSSMF information registered to ESR. 3. There is one slice service that is activated.	Login to UUI portal , and visit the "5G Slicing Management"/"Communication Service " Page. Select the Communication Service Click "Deactivate"	1.In "5G Slicing Management"/"Communication Service " the slice service is there , and the status changed to "deactivated".	IN PROGRESSN INESS
8	Service termination (remove service profile/slice profile from NSI/NSSI)	1.NSST, NST, ServiceProfile Template, CST designed in SDC and distributed successful. 2.NSSMF information registered to ESR. 3. There is one slice service that is deactivated.	Login to UUI portal , and visit the "5G Slicing Management"/"Communication Service " Page. Select the Communication Service Click "terminate"	1.In "5G Slicing Management"/"Communication Service " the slice service is deleted. 2.In "5G Slicing Management"/"Slicing Resource Management/Slicing Business Management" the service is deleted 3.In "5G Slicing Management"/"Slicing Resource Management/Slicing Instance Management" the NSI for this service is there. view detail you cannot find the service attached to the NSI any more.	COMPLETED
9	Service instantiation request via ExtAPI (using postman) - resulting in new NSI to be instantiated	1.NSST, NST, ServiceProfile Template, CST designed in SDC and distributed successful. 2.NSSMF information registered to ESR. 3.there is new NSI and NSSI already support the service. 4.OOF policy set so that the new NSI/NSSI can be returned.	1.Use postman to call external api to call the instantiate request. 2.Visit "5G Slicing Management"/"Slicing Task management" Page. 3.Find the task for the network slice, click "Process Task" to deal with it. 4.User check the orchestration results,, and fill the script Name for every domain. 5.Click OK to confirm the processing.	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 Management/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 Management/Slicing Subnet Instance Management" the new NSSI is there. view detail you can find the NSSI is connected to the NSI.	IN PROGRESS	Using POSTMAN, EXT-API↔SO interactions are verified. E2E flow is yet to be tested - will be checked once test case #3 is completed.
10	Service instantiation request via ExtAPI (using postman) - resulting in reuse of existing NSI	1.NSST, NST, ServiceProfile Template, CST designed in SDC and distributed successful. 2.NSSMF information registered to ESR. 3.there is new NSI and NSSI already support the service. 4.OOF policy set so that the shared NSI can be returned.	1.Use postman to call external api to call the instantiate request. 2.Visit "5G Slicing Management"/"Slicing Task management" Page. 3.Find the task for the network slice, click "Process Task" to deal with it. 4.User check the orchestration results,, and fill the script Name for every domain. 5.Click OK to confirm the processing.	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 Management/Slicing Business Management" the service is there. 4.In "5G Slicing Management"/"Slicing Resource Management/Slicing Instance Management" the shared NSI is there. view detail you can find the new service attached to the NSI.	IN PROGRESS	Using POSTMAN, EXT-API↔SO interactions are verified. E2E flow is yet to be tested - will be checked once test case #4/#5 is completed.