Test Plan - Functional
Last Update:
by:
Test Suite Description:
The main goal of the functionality test is to verify if the ONOS package is working correctly. Functionality test focuses on testing the intent framework which allows us to build different scenarios in the network topology that ONOS should be able to handle. A test run covers from network discovery to rerouting flows by changing the network topology during the test. We verify the results by analyzing ONOS state before and after each scenarios as well as confirming hosts reachability.
Functionality Tests Scenarios:
ProdFunc:Single instance, distribute core, OVS1.0
ProdFunc:Single instance, distribute core, OVS1.3
MultiProd:Multi instance, distributed core, OVS1.0
MultiProd:Multi instance, distributed core, OVS1.3
ID | Description | Mode | Passing Criteria | TestON Test | TestON Case | Roadmap |
FN-1 | Starting single instance ONOS, install ONOS, start onos-service and obtain all the component (ONOS bench, ONOScli,ONOS instance, Mininet) handles | Reactive | check Karaf Log with "onos started" |
| CASE 1 | Now |
FN-2 | Assign mastership to controller | Reactive |
|
| CASE 4 | Now |
FN-3 | Host Discovery before adding intents | Reactive |
|
| CASE 4 | Now |
FN-4 | Point Intent Addition (matching on port numbers) | Proactive |
|
| CASE 9 | Now |
FN-5 | Host Intent Addition | Proactive |
|
| CASE 6 | Now |
FN-6 | Compare ONOS topo & mininet topo | Proactive | Using STS, verify if the topology across all nodes is consistent with mininet's view of topology |
| CASE 5 | Now |
FN-7 | Link discovery consistency - | Proactive |
|
| CASE 7 | Now |
FN-8 | Verify Intents with VLAN-id | Proactive |
| None | None | In Progress |
FN-9 | Link Discover using BDDP; Steps:
| Proactive | ONOS reports topo matches MN topo | None | None | In Progress |
FN-10 | Rewrite mac address action in multi point to single point intent | Proactive |
|
| CASE 33 | Now |
FN-11 | Remove previously added intents before adding new type of intents | Proactive |
|
| CASE 8 | Now |
FN-12 | Link up/down discovery | Proactive |
|
| CASE 7 | Now |
FN-13 | Implement test script for one hop point intent | Proactive |
|
| CASE 11 | Now |
FN-14 | Point intent related SDN-IP matching on ICMP (SDN-IP use case related intent) | Proactive |
|
| CASE 31 | Now |
FN-15 | Point intent related SDN-IP matching on TCP (SDN-IP use case related intent) | Proactive |
|
| CASE 32 | Now |
FN-16 | MultiPoint to single point intent related SDN-IP matching on IP prefix and rewriting mac address | Proactive |
|
| CASE 33 | Now |
FN-17 | Connect Packet Optical topology to ONOS. Here, incase of Packet Optical, the links are not learnt from the topology, instead the links are learnt from the json config file | Proactive |
|
| CASE 21 | Now |
FN-18 | Compare ONOS topology view with the spawned Packet Optical topology | Proactive |
|
| CASE 22 | Now |
FN-19 | Add bidirectional point intents between 2 packet layer(mininet) devices
| Proactive |
|
| CASE 23 | Now |
FN-20 | Test Rerouting of Packet Optical by bringing an optical port down on a ROADM | Proactive |
|
| CASE 24 | Now |
FN-21 | Switch down discovery | Proactive | Verify if the switch availability is FALSE in "devices" cli command |
| CASE 2 | Now |