Have questions? Stuck? Please check our FAQ for some common questions and answers.

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 31 Next »

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.

Test Topology:

Functionality Test Suites

 

Test SuiteTest CasesPassing CriteriaRoad Map
Intent Functionality (FUNCintent)Host intent
  • Intents can be installed between network nodes
  • Connectivity between hosts when intents are installed
  • Intent state is in INSTALLED state for each active instances
  • All devices that are being used are in ACTIVE state
  • Each active device are assigned to one master controller
  • Network topology from Mininet is equivalent to ONOS view for each active instances
  • Flows should be in its appropriate state before and after an event such as intent installation, rerouting flows etc.
  • System state is consistent to all active ONOS instance
  • Connectivity is preserved in rerouting flows when particular links are down
  • Every match action given when adding intents should correctly stored in each of intents status
  • Network nodes ( switch and host ) information are consistent such as MAC, IPs, IDs, Ports.
  • All steps and verification should pass with different types of host: Dual stack, IPV4, VLAN etc.
  • Completely remove or purge all intents that have been installed
Now
 Point intentNow
 Multi-to-single point intentNow
 Single-to-multi point intentNow

 

 

  • No labels