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:
...
ID
...
Description
...
Mode
...
Prio
...
Passing Criteria
...
TestON Test
...
TestON Case
...
Roadmap
...
...
Test suites:
- 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
...
...
...
...
...
...
...
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
...
Controller assignment to the switches
...
Reactive
...
...
Using the command sh ovs-vsctl get-controller {swName}
...
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
The main goal of the functionality test suits is to verify if the ONOS package is working correctly. Functionality tests focus on testing the 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 mini net'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
...
Low
...
...
...
...
Sprint?
...
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
...
?
...
Low
...
ONOS reports topo matches MN topo
...
None
...
None
...
Sprint?
...
FN-10
...
Rewrite mac address action in multi point to single point intent
...
Proactive
...
High
...
- Verify using "intents" cli command where the intent's state should be INSTALLED
...
MultiProd
MultiProd13
...
CASE 33
...
Sprint1
...
FN-11
...
Remove previously added intents before adding new type of intents
...
Proactive
...
High
...
- 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
...
Sprint1
...
FN-12
...
Port up/down discovery
...
...
High
...
- 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
...
...
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
...
- 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
...
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
...
- 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
...