Page History

...

This test uses pingall function , from the mininet driver, to ping all the host in the network. The test is successful if all the hosts are reachable.

• CASE1: Starts up ONOS, from pulling the latest code to running ONOS, also starts a Mininet topology from the .topo file. Reports success if ONOS did not start starts up correctly.
• CASE2: Assign mastership to controller. Reports success if all the switches are assigned to a controller.
• CASE3: Installs onos-app-fwd (reactive forwarding app) and does pingall. Reports success if all hosts are reachable.

...

The <testcases> tag defines the order in which the test cases in the .py file are executed. The <cellName> is the name of the cell when setting up your environment. <PARAMS> and <testcases> are mandatory tags and the tags are case sensitive.

Topo File

Below is the PingallExample.topo file:

...

The .topo file includes the log in info of the machine that the ONOS and Mininet will be run. In this example, the test runs using two VM machine with host IP, user name , password as well as the driver that will be used are defined for each of the component. The <connect_order> tag is the connection order that the TestON will execute. The formatting of the .topo file must be followed correctly. The space character inside every empty tag indicates that a blank information will be passed along in the component otherwise the test would give an error , if that space character isn't there, and would stop the test. The <type> tag is use to specify which driver the component will use. The <args> tag in the MIninet component is necessary and should be kept even though have empty argumentsit has empty arguments. In the Topo file, all the tags are necessary but the driver specific tags can be placed between the components tags.

NOTE: It is important to check the log in info carefully for each component as incorrect information would result to test failure.

...