You can see test files in the /TestON/tests/ folder. Each of the tests has a unique set of files defined below:
Topo .topo - This file defines all the components and options that Test-ON will use to execute its test. The machine's user name, password, IP addresses, drivers, and/or Mininet's topology would be specified in this file. ( Please use the exact syntax/format in the topo file. The space character in the xml tags is important even though you are not defining anything in the tag Eg. <COMPONENTS> </COMPONENTS>)
.py - This is where all of the test cases are written. It calls upon functions implemented in the respective drivers to create a progression of events that produces some sort of pass/fail outcome.
This test uses pingall function to ping all the host in the network. The test is successful if all the hosts are reachable.
- CASE1CASE1: Starts up ONOS, from pulling the latest code to running ONOS
- , also starts the a Mininet instance. Reports success if ONOS did not start 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.
Below is the PingallExample.params:
<PARAMS> <testcases>1,2,3</testcases> <ENV> <cellName>HA</cellName> </ENV> <Git>True</Git> <CTRL> <ip1>10.128.30.11</ip1> <port1>6633</port1> </CTRL> </PARAMS>