Test Plan - Functional

ID

Description

Mode

Prio

Passing Criteria

TestON Test

TestON Case

Roadmap

Single instance, distribute core

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

CASE 4

Now

FN-3
 

Host Discovery before adding intents

Reactive

• Verify using "hosts" cli command
• Pingall command

ProdFunc
ProdFunc13

CASE 4

Now

FN-4

Point Intent Addition (matching on port numbers)

 

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

CASE 9

Now

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

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

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

CASE 7

Now

FN-8

Switch down discovery

Proactive

High

• Compare MN topo and ONOS topo
• Ping

FN-9

Verify Intents with VLAN-id

Proactive
Reactive

Low

Sprint?

FN-10

Link Discover using BDDP; Steps:

1. setup a test topo with non-OF Br connected two OF topo
2. let ONOS discover the topo;
3. compare ONOS topo and Mininet Topo

?

Low

ONOS reports topo matches MN topo

None

None

Sprint?

FN-11

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
• Ping between the hosts connected to the devices between whom point intents were added should pass

Sprint1

FN-12

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

CASE 8

Sprint1

FN-13

Point to Point Intent Addition matching on TCP

Proactive

•  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

CASE 32

Now

FN-14

Port up/down discovery

High

Compare MN topo and ONOS topo
Ping
?

CASE 7

Now

1. ONOS-151