...
Category: External System Registration
T00001: WindRiver OpenStack VIM Registration
T00001| T101 |
| Test Case Name | WindRiver OpenStack VIM Registration |
| Description | WindRiver OpenStack VIM Registration |
| Release | Amsterdam |
| Preconditions | - The WindRiver OpenStack VIM is configured with tenant information and provider networks
- The WindRiver OpenStack VIM services (console, auth, neutron, image, glance, etc) are accessible from ONAP by IP
|
| Testing Steps | - Add VIM from ONAP GUI with VIM location information, tenant authentication information
- VIM default service url can be configured based on real VIM settings
|
| Expected Results | - VIM is registered successfully
- Tenant authentication information is stored correctly
|
| Actual Results |
|
| Conclusion (Pass/Fail) |
|
| Testing Lab |
|
| Tester Name |
|
Category: VNF Onboarding and Service Creation
T00002: vCPE VNFs Onboarding
T00002| T201 |
| Test Case Name | vCPE VNFs Onboarding |
| Description | Onboard vDHCP, vAAA, vDNS, WebServer, vBRG, vBNG, vGMux, vG |
| Release | Amsterdam |
| Preconditions | - All HEAT and TOSCA templates are ready
- VNF license has been created
|
| Testing Steps | - Use SDC to import, test and certify the following VNF templates, including both yaml and env files: vDHCP, vAAA, vDNS, WebServer, vBRG, vBNG, vGMux, vG
|
| Expected Results | - All VNFs are onboarded successfully
|
| Actual Results |
|
| Conclusion (Pass/Fail) |
|
| Testing Lab | WindRiver Lab |
| Testing Date |
|
| Tester Name |
|
T00003: vCPE Service Creation
T00003| T202 |
| Test Case Name | vCPE Service Creation |
| Description | This creates vCPE service |
| Release | Amsterdam |
| Preconditions | - All VNFs have been onboarded
- All VNFs images files have been uploaded manually into VIM
|
| Testing Steps | - Use SDC to create core infrastructure service including
|
DHCP AAA DNS- vDNS, and Web server
- Use SDC to create a service including vBNG
- Use SDC to create a service including vGMux
- Use SDC to create a service including vBRG
- Use SDC to create a service including vG
|
| Expected Results | - Each service is created successfully and stored in the catalog
|
| Actual Results |
|
| Conclusion (Pass/Fail) |
|
| Testing Lab | WindRiver Lab |
| Testing Date |
|
| Tester Name |
|
T00004: Closed Loop Configuration
T00004| T203 |
| Test Case Name | Closed loop configuration |
| Description |
This test will be completed after the CLAMP R1 plan is finalized | Create and distribute closed loop artifacts from CLAMP
|
| Release | Amsterdam |
| Preconditions | - ONAP platform up and running
|
| Testing Steps | - Use CLAMP Cockpit to create closed loop control for vCPE
- Distribute the results to policy and DCAE (through SDC)
|
| Expected Results | - Verify and the policy is distributed to Policy Engine
- Verify that Blueprint template and meta data (including service UUID, resource UUID, and artifact name) distributed to DCAE inventory
|
| Actual Results |
|
| Conclusion (Pass/Fail) |
|
| Testing Lab | WindRiver Lab |
| Testing Date |
|
| Tester Name |
|
Closed Loop Deployment
| Test Case ID | T204 |
| Test Case Name | Closed loop deployment |
| Description | Deploy and activate closed loop control for vCPE |
| Release | Amsterdam |
| Preconditions | - Closed loop configuration completed in T203
|
| Testing Steps | - From CLAMP Cockpit, user chooses to deploy vCPE closed loop control
|
| Expected Results | - DCAE responds by bringing up a VES collector container, loading TCA app to CDAP, and configuring DMaaP to enable data flow from VES collector to TCA.
|
| Actual Results |
|
| Conclusion (Pass/Fail) |
|
| Testing Lab | WindRiver Lab |
| Testing Date |
|
| Tester Name |
|
Category: Service Instantiation and Monitoring
T00005: Infrastructure Service Instantiation
T00005| T301 |
| Test Case Name | vCPE Infrastructure Service Instantiation |
| Description | This test covers the infrastructure service instantiation process, including DHCP, AAA, DNS, Webserver, vBNG, and vGMux. |
| Release | Amsterdam |
| Preconditions | - vCPE services have been created
- Closed loop has been configured
|
| Testing Steps | - ONAP user uses VID to instantiate DHCP, AAA, DNS, and Webserver
- ONAP user uses VID to instantiate vBNG
- ONAP user use Robot to instantiate vGMux
|
| Expected Results | - DHCP, AAA, DNS, and Web Server are up and running
- vBNG is up and running
- vGMux is up and running
- The network connection all the above VNFs are created successfully
- The closed loop is up and running, DCAE can collect packet loss rate from vGMux and send analytics results to Policy
|
| Actual Results |
|
| Conclusion (Pass/Fail) |
|
| Testing Lab | WindRiver Lab |
| Testing Date |
|
| Tester Name |
|
T00006: Customer Service Instantiation
T00006| T302 |
| Test Case Name | vCPE Customer Service Instantiation |
| Description | This test covers the customer service instantiation process, including vBRG emulator and vG and the related configuration. |
| Release | Amsterdam |
| Preconditions | - vCPE services have been created
- vCPE infrastructure service has been instantiated
|
| Testing Steps | - ONAP user uses VID to instantiate a vBRG and a VM that is connected to the vBRG
- Once vBRG is instantiated, its subsequent DHCP request will invoke ONAP to instantiate a vG and complete all required configuration. This step does not require human intervention.
- ONAP user sign on to the VM connected to the vBRG and test connection to the web server.
|
| Expected Results | - vBRG and vG are up and running
- ONAP user can access the web server
|
| Actual Results |
|
| Conclusion (Pass/Fail) |
|
| Testing Lab | WindRiver Lab |
| Testing Date |
|
| Tester Name |
|
Category: Closed Loop
T00007: vCPE Auto-healing
T00007| T401 |
| Test Case Name | vCPE Auto-healing |
| Description | This test covers the closed loop to restart vGMux when packet loss is detected. |
| Release | Amsterdam |
| Preconditions | - vCPE service instantiated
- Customer service instantiated
- Close loop is up and running
|
| Testing Steps | - Use Robot to invoke vGMux to generate packet loss event
- The event will trigger self-healing, the process is automatic and does not require human intervention
|
| Expected Results | - DCAE captures packet loss event and sends event to Policy
- Policy invokes APPC to restart the vGMux VM
- vGMux VM is restarted
- Web server access from customer is disrupted during restarting and restored afterwards
|
| Actual Results |
|
| Conclusion (Pass/Fail) |
|
| Testing Lab | WindRiver Lab |
| Testing Date |
|
| Tester Name |
|
Category: Service Termination
T00008: vCPE Service Termination
T00008| T501 |
| Test Case Name | vCPE Service Termination |
| Description | This test covers vCPE service termination process |
| Release | Amsterdam |
| Preconditions | - vCPE service is created
- Closed loop is established
|
| Testing Steps | - ONAP user uses Usecase UI GUI to remove vCPE service
|
| Expected Results | - Closed loop is stopped
- All vCPE VNFs and VLs are removed
- DCAE collector container removed and the analytics application unloaded.
- Closed loop related artifacts (including DCAE template and policy) are removed from ONAP
|
| Actual Results |
|
| Conclusion (Pass/Fail) |
|
| Testing Lab | WindRiver Lab |
| Testing Date |
|
| Tester Name |
|