Components in this Setup:

• Jenkins CI system (Optional - if you need to have automated build job set up; else, all the test cases can be driven from TestStation.);
• Wiki (Atlassian Confluence), or other publishing services (Optional - if you do need to publish test results);
• Connection to Gerrit Repo - gerrit.onosproject.org
• TestStation - we use a single VM/server to run TestON together with ONOS test bench;
• ONOS cells - each cell is a node running ONOS - the number of cells needed depending on your test cases; we are currently running one cell per VM;
• Openflow network - this is either a Mininet-emulated network, or physical network.

Test Setup Procedure:

1. Setting up ONOS test bench and cells according to the "getting started" guide in "ONOS for Newcomers";
2. Clone https://github.com/OPENNETWORKINGLAB/ONLabTest to the TestStation:  "git clone https://github.com/OPENNETWORKINGLAB/ONLabTest"

Notes:

• ONOS system testing adopted the TestON framework created by Paxterra, with a number of modifications that fit the test environment for ONOS tests. You can find the original TestON framework at: https://github.com/Paxterra/TestON
• For the ONOS project, we created a new repository that is forked from the original TestON with substantial modifications on drivers. ONOS specific test cases are also periodically recommitted back to this repository. You can find the public repository here: https://github.com/OPENNETWORKINGLAB/ONLabTest.
• Since test cases and environments can substantially affect how the system test cases are run. The test plan and corresponding test cases on this wiki can be used as a reference for you to build your own system test.