commit | dd3b0e4d4ce9d9bc6a70eca4ce963ccb41e62ee9 | [log] [tgz] |
---|---|---|
author | pingping-lin <pingping@onlab.us> | Tue Dec 02 11:46:54 2014 -0800 |
committer | pingping-lin <pingping@onlab.us> | Tue Dec 02 11:46:54 2014 -0800 |
tree | e1db7fed61acce4598c8df5a429900eabaf6da45 | |
parent | c6b86fabfb3ac2bd365fe1c1c79acbd01064db72 [diff] |
improve the code to make it more readable
TestON is the testing platform that all the ONOS tests are being run on currently.
Pull the git repo from https://github.com/OPENNETWORKINGLAB/ONLabTest.git
$ git clone https://github.com/OPENNETWORKINGLAB/ONLabTest.git
Make a symbolic link for TestON on the HOMEDIR Execute the following from the home directory
$ ln -s ONLabTest/TestON TestON
Make sure python path is correct
$ export PYTHONPATH={PATH TO HOMEDIR}/TestON/
$ echo $PYTHONPATH
ONOS
Mininet
Install python packages configObj and pexpect. they can be installed as :
$ sudo pip install configObj
$ sudo easy_install pexpect
Config file at TestON/config/teston.cfg
Change the file paths to the appropriate paths
The .topo file for each test
Must change the IPs/login/etc to point to the nodes you want to run on
TestON must be ran from its bin directory
$ cd TestON/bin
Launch cli
$ ./cli.py
Run the test
teston> run MininetTest
The tests are all located it TestON/tests/ Each test has its own folder with the following files:
.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
.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
.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.
.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.
Here are a few things to check if it doesn't work
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)
Enable passwordless logins between your nodes and the TestON node.