Due to a ransomware attack, the wiki was reverted to a July 2022 version. . We apologize for the lack of a more recent valid backup.
Test Plan - Functional
Last Update:
by:
Test Suite Description:
The main goal of the functionality test suits is to verify if the ONOS package is working correctly. Functionality test focuses tests focus 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
(with app-fwd installed)
...
check Karaf Log with "onos started"
...
- ProdFunc
- ProdFunc13
- MultiProd
- MultiProd13
...
CASE 1
...
Now
...
FN-2
...
Assign mastership to controller
...
Reactive
...
- Verify mastership using the command sh ovs-vsctl get-controller { switch name }
...
- ProdFunc
- ProdFunc13
- MultiProd
- MultiProd13
...
CASE 4
...
Now
...
FN-3
...
Host Discovery before adding intents
...
Reactive
...
- Verify using "hosts" cli command
- Pingall command
...
- ProdFunc
- ProdFunc13
- MultiProd
- MultiProd13
...
CASE 4
...
Now
...
FN-4
...
Proactive
...
- Verify using "intents" cli command where the intent's state should be INSTALLED
- Ping between the hosts connected to the devices between whom point intents were added should pass
...
- ProdFunc
- ProdFunc13
- MultiProd
- MultiProd13
...
CASE 9
...
Now
basic functionality of ONOS and core applications.
For more details on each section of the functionality test suites please look to the sub pages
| Page Tree | ||
|---|---|---|
|
...
FN-5
...
Host Intent Addition
...
Proactive
...
- Verify using "intents" cli command where the intents' s state should be INSTALLED
- Ping between the hosts connected to the devices between whom host intents were added should pass
...
- ProdFunc
- ProdFunc13
- MultiProd
- MultiProd13
...
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
...
- ProdFunc
- ProdFunc13
- MultiProd
- MultiProd13
...
CASE 5
...
Now
...
FN-7
...
Link discovery consistency -
Bring a mininet link down and then up
...
Proactive
...
- Continuous ping
- Compare Mininet topo and ONOS topo and
- Verify from the "topology" cli command output, if the number of links are -2 when link down is implemented and same number of links before bringing down the link when link up is implemented
...
- ProdFunc
- ProdFunc13
- MultiProd
- MultiProd13
...
CASE 7
...
Now
...
FN-8
...
Verify Intents with VLAN-id
...
Proactive
Reactive
...
- Install host, point, single point to multi points and multi points to single point intents using VLAN hosts
- Verify from "hosts" command if ONOS discover correct VLAN tag
- Verify using "intents" cli command where the intents' s state should be INSTALLED
- Ping between the hosts connected to the devices between whom intents were added should pass
...
None
...
None
...
In Progress
...
FN-9
...
Link Discover using BDDP; Steps:
- setup a test topo with non-OF Br connected two OF topo
- let ONOS discover the topo;
- compare ONOS topo and Mininet Topo
...
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
...
- Verify using "intents" cli command where the intent's state should be INSTALLED
...
- MultiProd
- MultiProd13
...
CASE 33
...
Now
...
FN-11
...
Remove previously added intents before adding new type of intents
...
Proactive
...
- Verify using "intents" cli command where the intents should be removed(vanished)
- Ping between the hosts connected to the devices between whom point intents were removed should fail
...
- ProdFunc
- ProdFunc13
- MultiProd
- MultiProd13
...
CASE 8
...
Now
...
FN-12
...
Link up/down discovery
...
Proactive
...
- Continuous ping
- Compare Mininet topo and ONOS topo and
- Verify from the "topology" cli command output, if the number of links are -2 when link down is implemented and same number of links before bringing down the link when link up is implemented
...
- ProdFunc
- ProdFunc13
- MultiProd
- MultiProd13
...
CASE 7
...
Now
...
- Move host from one switch to another to form a switch with 2 host
- Add a one hop point intent between the two host
- Verify using "intents" cli command where the intents should be removed(vanished)
- Ping between the hosts connected to the devices between whom host intents were added should pass
...
- ProdFunc
- ProdFunc13
...
Point intent related SDN-IP matching on ICMP
(SDN-IP use case related intent)
...
- Verify using "intents" cli command where the intent's state should be INSTALLED
- Ping between the hosts connected to the devices between whom point intents were added should pass
...
- MultiProd
- MultiProd13
...
Point intent related SDN-IP matching on TCP
(SDN-IP use case related intent)
...
- Verify using "intents" cli command where the intent's state should be INSTALLED
- iperf test between the hosts connected to the devices between whom point intents were installed should pass
...
- MultiProd
- MultiProd13
...
- Verify using "intents" cli command where the intent's state should be INSTALLED
- Ping between the hosts connected to the devices between whom point intents were removed should pass
...
- MultiProd
- MultiProd13
...
Here, incase of Packet Optical, the links are not learnt from the topology, instead the links are learnt from the json config file
...
- Verify if the LINC-OE cli is started successfully
- Verify if the json config file is successfully pushed
...
- ProdFunc
- ProdFunc13
- MultiProd
- MultiProd13
...
- Verify if the Optical ROADM's and Packet layer mininet devices are discovered from the "devices" cli command
- Verify if the Optical links are discovered from the "links" cli command
...
- ProdFunc
- ProdFunc13
- MultiProd
- MultiProd13
...
Add bidirectional point intents between 2 packet layer(mininet) devices
...
- Verify using "intents" cli command where the intent's state should be INSTALLED
- Ping between the hosts connected to the devices between whom point intents were added should pass
...
- ProdFunc
- ProdFunc13
- MultiProd
- MultiProd13
...
- Verify using the "ports" cli command if the port that was taken down shows DISABLED
- Verify using the "links" cli command if the corresponding links become inactive
- Ping between the hosts connected to the devices between whom point intents were added should pass which verifies the rerouting
...
- ProdFunc
- ProdFunc13
- MultiProd
- MultiProd13
...
- ProdFunc
- ProdFunc13
...