Gitiles
Code Review Sign In
gerrit.onosproject.org / OnosSystemTest / be6dfc4e213e03dab83e54e10332fec255a3218a
commitbe6dfc4e213e03dab83e54e10332fec255a3218a[log] [tgz]
authorJon Hall <jhall@onlab.us>Mon Jan 12 17:37:25 2015 -0800
committerJon Hall <jhall@onlab.us>Mon Jan 12 17:37:25 2015 -0800
treec4645cc55f328c6c3c4eb434a598dc10d59c4958
parentca74262e65985789a191b7cf9b50eff0c0b04ded [diff]
Note custom mn dependencies
1 file changed
tree: c4645cc55f328c6c3c4eb434a598dc10d59c4958
  1. .gitignore
  2. README.md
  3. TestON/
README.md

TestON, a testing infastructure by Paxterra

TestON is the testing platform that all the ONOS tests are being run on currently.

Setup

  1. Pull the git repo from https://github.com/OPENNETWORKINGLAB/ONLabTest.git

    $ git clone https://github.com/OPENNETWORKINGLAB/ONLabTest.git

  2. Make a symbolic link for TestON on the HOMEDIR Execute the following from the home directory

    $ ln -s ONLabTest/TestON TestON

  3. Make sure python path is correct

    $ export PYTHONPATH={PATH TO HOMEDIR}/TestON/

    $ echo $PYTHONPATH

Dependencies

  1. ONOS

  2. Mininet - Some driver functions rely on a modified version of Mininet. These functions are noted in the mininet driver file. To checkout this branch from your Mininet folder:

    $ git remote add jhall11 https://github.com/jhall11/mininet.git

    $ git fetch jhall11

    $ git checkout -b dynamic_topo remotes/jhall11/dynamic_topo

    $ git pull

    Note that you may need to run 'sudo make develop' if your mnexec.c file changed when switching branches.

  3. Install python packages configObj and pexpect (Note: pexpect 3.3 has a known bug. We recommend using version 3.2 for now). They can be installed as :

    $ sudo pip install configObj

    $ sudo pip install pexpect==3.2

  4. STS - This can be installed by:

    $ git clone https://github.com/jhall11/sts.git

Configuration

  1. Config file at TestON/config/teston.cfg

    Change the file paths to the appropriate paths

  2. The .topo file for each test

    Must change the IPs/login/etc to point to the nodes you want to run on

Running TestON

  1. TestON must be ran from its bin directory

    $ cd TestON/bin

  2. Launch cli

    $ ./cli.py

  3. Run the test

    teston> run MininetTest

The Tests

The tests are all located it TestON/tests/ Each test has its own folder with the following files:

  1. .ospk file

    • This is written in Openspeak, a word based language developed by Paxterra.

    • It defines the cases and sequence of events for the test

  2. .py file

    • This file serves the same exact function as the openspeak file.

    • It will only be used if there is NO .ospk file, so if you like python, delete or rename the .ospk file

  3. .topo file

    • This defines all the components that TestON creates for that test and includes data such as IP address, login info, and device drivers

    • The Components must be defined in this file to be uesd in the openspeak or python files.

  4. .params file

    • Defines all the test-specific variables that are used by the test.

    • NOTE: The variable testcases which defines which testcases run when the test is ran.

Troubleshooting

Here are a few things to check if it doesn't work

  1. Double check the topo file for that specific test the nodes must be able to run that specific component ( Mininet IP -> machine with mn installed)

  2. Enable passwordless logins between your nodes and the TestON node.