Gitiles
Code Review Sign In
gerrit.onosproject.org / OnosSystemTest / 9aaba88d7134703460e62b7b16c2881d4ef513b0
commit9aaba88d7134703460e62b7b16c2881d4ef513b0[log] [tgz]
authorJon Hall <jhall@onlab.us>Mon Jan 19 15:05:15 2015 -0800
committerJon Hall <jhall@onlab.us>Wed Jan 21 13:59:40 2015 -0800
treecf4230788b39d02b2d7152663ad8b03c8438e66d
parent5af6e47763b824165d3028bbfebaef551c6f8812 [diff]
parent9d1ec74e3b28404db4bc335525926e59e8bc1b4e [diff]
Merge branch 'devl/cleanup' of https://github.com/OPENNETWORKINGLAB/ONLabTest into cleanup

Conflicts:
	TestON/drivers/common/cli/onosdriver.py
	TestON/drivers/common/clidriver.py
tree: cf4230788b39d02b2d7152663ad8b03c8438e66d
  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

  3. Install python packages configObj and pexpect. they can be installed as :

    $ sudo pip install configObj

    $ sudo easy_install pexpect

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, an 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.