Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Test Plan - Functional

Last Update: 
by: 

...

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

...

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

...

 

...

Pingall

...

ProdFunc
ProdFunc13

...

CASE 4

...

Now

...

FN-4

...

Point Intent Addition (matching on port numbers)
Bugs discovered- 1)Overlapping flow rules
2) Overlapping flow match conditions
 

...

Proactive

...

 

...

ping between the hosts

...

ProdFunc
ProdFunc13

...

CASE 4

...

Now

...

FN-5

...

Host Intent Addition

...

Proactive

...

 

...

ping between the hosts

...

ProdFunc
ProdFunc13

...

CASE 4

...

Now

...

FN-6

...

Compare ONOS topo & mininet topo

...

Proactive

...

 

...

using STS

...

ProdFunc
ProdFunc13

...

CASE 7,5

...

Now

...

FN-7

...

Link discovery consistency -
Bring a mininet link down and then up

...

Proactive

...

 

...

  • Continuous ping
  • Compare MN topo and ONOS topo and
  • Verify from the topology 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

...

 

...

  • Compare MN topo and ONOS topo
  • Ping

...

 

...

 

...

 

...

FN-9

...

Verify Intents with VLAN-id

...

Proactive
Reactive

...

Low

...

 

...

 

...

 

...

Sprint32

...

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 reportes topo matches MN topo

...

None

...

None

...

Sprint32

...

FN-11

...

Rewrite actions in intents
(sync up with Jono)

...

?

...

High

...

 

...

 

...

 

...

Sprint32

...

FN-12

...

Point to Point Intent Addition (match on arbitrary fields, may be ip)

...

 

...

Medium

...

 

...

 

...

 

...

Sprint32

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
rootTest Plan - Functionality (FUNC*)

...

FN-14

...

Port up/down discovery

...

 

...

Medium

...

Compare MN topo and ONOS topo
Ping
?

...

 

...

 

...