Image Added

System Test Setup Overview

Created by: ; Last Modified by: ; Last Update: 

Image Removed

Components in this Setup:

...

Example Test Setup Procedure:

This procedure assume TestStation is running OnosSystemTest, onos bench, and Mininet; Host[1~7] are running onos cell OC[1-7].

...

guide will help you install TestON, configure your environment, and run a sample test with a three node cluster.

Requirements: ONOS 1.3 or higher (recommended) must be correctly installed. Follow this guide to install ONOS.

Clone Mininet to TestStation and run the install script

$ cd ~
$ git clone https://github.com/jhall11/mininet.git	    # Clone the repository
$ cd mininet
$ git branch -v -a									    # Show all the remote repositories
$ git checkout -b dynamic_topo origin/dynamic_topo		# Checkout the dynamic_topo repository
$ cd util
$ sudo ./install.sh -3fvn								# Install OpenFlow 1.3, Open Vswitch and Mininet dependencies

...

NOTE: If you have a different repo of Mininet, we recommend removing it and re-cloning the one listed above. You will also need to remove these packages from your home dir: pox, loxigen, openflow, flop, oftest, openvswitch, and any other package that mininet installs. Refer to this page if you any questions 

http://mininet.org/download/.

Clone "OnosSystemtest" to

...

TestStation 

$ git clone https://gerrit.onosproject.org/OnosSystemTest

...

Install TestON

Please follow TestON installation guide to install TestON.

Set your cell. The sample test requires a 3-node cell. Follow this guide if you are having trouble setting your cell.

NOTE: The cell needs OC1-3 defined, OCN to point to your bench test station, and OCI to point to OC1. 

$ cell <cell name>

NOTE: Make sure ONOS is update-to-date and you build it before running the test.

Run the sample test.

$ cd ~/OnosSystemTest/TestON/bin/
$ ./cli.py run SAMPstartTemplate_1node

TestON Scripting General Guidelines:

 Due to the many components required for system tests, it is possible that one tester's environment can be drastically different from another's.  In ONLAB, we have a production test environment to run the current published test suites. In time, we expect the community to contribute to improving the test suites, or creating new test suites that will also be run on this env. We set up a set of test development guideline to achieve the following objectives:

...

Portability:

• testers should be able to clone the tests; set up system environment variables accordingly; and run the tests without test script modifications;

• contributors should be able to commit changes and new test suites to be run on ONLAB production testbed.

...

Stability:

• robust - i.e. minimize script-causing test failures;

• In depth onos application state verification.

...

Clarity:

...

tests should produce useful onos failure information for further debug;

...

reports should provide a glance of onos health from each suite

Standardize driver & tests documentation.

...