MDONS Integration Test Case
1.Introduction
This is the integration test cases for CCVPN-MDONS use case.
Test effort and official documentation is tracked and maintained through the following story in JIRA.
2. Scope
The integration test case for MDONS use case, it includes third party controller registration, SDC design and service LCM.
3. Terms, definitions and abbreviations
Abbreviation | Full Name |
PNF | Physical Network Function |
DC | Domain Controller |
OTN | Optical Transport Network |
GUI | Graphic User Interface |
UNI | User Network Interface (NI) |
NNI | Network NI |
ENNI | External Network NI |
4. Test Framework
Module introduction:
ONAP | The ONAP system for automation operation. |
Domain Controller | A third party controller for L1/L0 network. |
5. Test description
The test for ONAP to L1 choreography of the business management, business deployment environment adopting physical manual deployment patterns, ONAP not deploy network, only do L1/OTN service LCM and L1 Node/PNF, Interface port/p-Interface automatically discover functions. The network elements of this test include 3rd domain controller and L1/L0 equipment.
5.1 Test Accounts
Name | Responsibility | Account |
Administrator | Responsible for system management; Personnel permission configuration; ONAP external system registration; Operational life cycle management | demo/demo123456! |
Designer | Service template design | cs0008/demo123456! |
Tester | Service template test | jm0007/demo123456! |
Governor | Service template approve | gv0001/demo123456! |
Operator | Service template distribution | op0001/demo123456! |
6. ONAP External System Registration Test
6.1 Domain Controller Registration
Test No: | TEST-01 |
Project: | ONAP ESR |
Sub Project: | 3rd domain controller registration |
Objective: | support domain controller registered to ESR-SDNC |
Pre-conditions: |
|
Test step:
| |
Test Result:
| |
Observation: When domain controller registered to ONAP. Wait for minutes, DC will synchronize the network topology to ONAP. Check the topology data of AAI. |
7. SDC Service Design
7.1 MDONS resource design
Test NO: | TEST-02 |
Project: | SDC Service Design |
Sub Project: | Resource import for MDONS |
Objective: | Support to import the resources for MDONS. |
Operator: | Designer, Tester |
Pre-conditions: |
|
Test step:
| |
Test Result:
| |
Observation: We can find new resources for MDONS in SDC portal |
7.2 MDONS Service Design
Test NO: | TEST-03 |
Project: | SDC Service Design |
Sub-project: | Design MDONS services: MDONS OTN Service |
Objective: | SDC support to design MDONS OTN services |
Pre-condition: |
|
Test step:
2. Enter the service general parameters?including name?category?select ‘L1-L3 Service’??description?contact ID?project code etc. click ‘Create” to create service template. ‘Saved successfully’ information will be shown. 3. Enter ‘Composition’ item?select resources needed for the service. 4. Enter ‘Properties Assignment’ item?config the parameters of the resources?click ‘Declare’ button to declare the parameters of resources as service inputs. 5. Click ‘submit for testing’? ‘Submitted for testing successfully’ will be shown. 6. Tester login to ONAP?click the service to test?and then click ‘start testing’ to test the service template. After test, click ‘accept’. 7. Governor login to ONAP to approve the service template. 8. Operator login to ONAP to distribute the service template. | |
Test result:
| |
Observation: |
8.Service LCM
8.1 L1/L0 TOPO Automatically synchronization.
Test NO: | TEST-04 |
Project: | Service LCM |
Sub-project: | L1/L0 network topology synchronized to ONAP |
Objective: | OTN network topology can be synchronized to ONAP, saved and mapped (TAPI, OpenRoadM) in A&AI. |
Pre-condition: |
|
Test steps:
| |
Test result:
| |
Observation: |
8.2 OTN cross-domain/cross-ONAP link management
Test NO: | TEST-05 |
Project: | Service LCM |
Sub-project: | L1/L0 network topology management |
Objective: | UUI can support to view the topology of network and create cross-domain/cross-ONAP links. |
Pre-condition: |
|
Test steps:
| |
Test result:
| |
Observation: |
8.3 OTN Service Instantiation
Test NO: | TEST-06 |
Project: | Service LCM |
Sub Project: | Service instantiation for OTN services |
Objective: | The OTN services can be instantiated. |
Pre-condition: |
|
Test step:
2.Click UUI item “Services”?and select ‘Services’ Tab. 3. Select customer and service type 4. Click ‘create’ to create services. 5. On ‘Create Service’ dialog, select the service template and enter the inputs for the service. 6. Click ‘OK’ to instantiate a OTN service. | |
Test Result:
| |
Observation:
It can connect to each other:
|
8.4 Service termination
Test NO: | TEST-07 |
Project: | Service LCM |
Sub-project: | Service termination for OTN services |
Objective: | The OTN services can be terminated. |
Pre-condition: |
|
Test step:
2. Click UUI item “Services”?and select ‘Services’ Tab. 3. Select customer and service type 4. Select service and click ‘delete’ to delete services. 5. Click ‘OK’ to terminate a service. 6. We need to delete the services. | |
Test Result:
| |
Observation:
|
9. Use Case Alignment
10. Issues Found
Component | Owner | Jira Ticket | Notes/Status |
---|---|---|---|
SO | @Seshu Kumar Mudiganti | ||
SDNC | |||
AAI | |||
UUI |