Page History

...

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

...

SAMPstartTemplate_1node and

...

SAMPstartTemplate_3node tests

These tests demonstrate several simple actions using TestON. The test is successful if all testcases succeed.

CASE0: Pulls ONOS code and builds ONOS. This is usually skipped in the production environment for flexibility to handle testing different versions of ONOS
CASE1: Sets up global test variables and removes existing instances of ONOS in the test cell
CASE2: Reports errors, warnings, and exceptions in ONOS
CASE10: Starts ONOS on the cell
CASE11: Start mininet and assign mastership of switches to ONOS controllers
CASE12: Tests some basic ONOS commands using the ONOS cli handle
CASE22: Tests some basic ONOS commands using the REST API handle
CASE32: Configure fwd app and run pingall

Params File

Below is the SAMPstartTemplate2SAMPstartTemplate_1node.params file:

Code Block

<PARAMS>
    <!--
    CASE0: pull onos code - this case should be skipped on Jenkins-driven prod test
    -->
    <!--
    CASE1: setup and clean test env
    -->
    <!--
    CASE2: get onos warnings, errors from log
    -->
    <!--
    CASE10: start a 1-node ONOS
    -->
    <!--
    CASE11: Start Mininet and assign controllers
    -->
    <!--
    CASE12: Sample case of using onos cli
    -->
    <!--
    CASE22: Sample case of using onos rest
    -->
    <!--
    CASE32: Configure fwd app
    -->
    <testcases>0,1,10,11,12,22,2<2,32</testcases>
    <CASE0>
        <gitPull>False</gitPull> # False or True
        <gitBranch>master</gitBranch>
    </CASE0>

    <CASE1>
        <NodeList>OC1,OC2,OC3</NodeList>
        <SleepTimers>
            <onosStartup>60</onosStartup>
            <onosCfg>5</onosCfg>
            <mnStartup>15</mnStartup>
            <mnCfg>10</mnCfg>
        </SleepTimers>
    </CASE1>

    <CASE10>
        <numNodes>1</numNodes>
        <Apps>
            org.onosproject.openflow,org.onosproject.fwd
        </Apps>
        <ONOS_Configuration>
            <org.onosproject.net.intent.impl.compiler.IntentConfigurableRegistrator>
                <useFlowObjectives>true</useFlowObjectives>
            </org.onosproject.net.intent.impl.compiler.IntentConfigurableRegistrator>
        </ONOS_Configuration>
    </CASE10>

    <CASE11>
        <path>~/OnosSystemTest/TestON/tests/SAMP/SAMPstartTemplate2_1node/Dependency/</path>
        <topo>newFuncTopo.py</topo>
    </CASE11>

    <CASE12>
    </CASE12>

    <CASE22>
    </CASE22>
 
    <CASE32>
    </CASE32>
</PARAMS>

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 SAMPstartTemplate2SAMPstartTemplate_1node.topo file:

Code Block

<TOPOLOGY>
 
    <COMPONENT>
 
    <!--
        This is a list of all components and their handles in the test setup.
        Even with some handles not used in test cases, we want to define
        all onos cells here, for cases to set up onos cluster.
    -->
 
        <ONOSbench>
            <host>localhost</host>
            <user>sdn</user>
            <password>rocks</password>
            <type>OnosDriver</type>
            <connect_order>1</connect_order>
            <COMPONENTS>
                <home></home> #defines where onos home is
            </COMPONENTS>
        </ONOSbench>
 
        <ONOScli1>
            <host>OC1</host>
            <user>sdn</user>
            <password>rocks</password>
            <type>OnosCliDriver</type>
            <connect_order>2</connect_order>
            <COMPONENTS>
            </COMPONENTS>
        </ONOScli1>
 
        <Mininet1>
            <host>localhost<<host>OCN</host>
            <user>sdn</user>
            <password>rocks</password>
            <type>MininetCliDriver</type>
            <connect_order>5</connect_order>
            <COMPONENTS>
                <home>~/mininet/custom/</home>
            </COMPONENTS>
        </Mininet1>
 
        <ONOSrest1>
            <host>OC1</host>
            <port>8181</port>
            <user>onos</user>
            <password>rocks</password>
            <type>OnosRestDriver</type>
            <connect_order>6</connect_order>
            <COMPONENTS>
            </COMPONENTS>
        </ONOSrest1>
 
    </COMPONENT>
 
</TOPOLOGY>

...

The python file defines all the test cases for the test. In the SAMPstartTemplate2 SAMPstartTemplate_1node and every other test in TestON, a utility class is called to assert each cases by the end of the case. Although not required, It is a good practice to follow a coding style in to your test scripts to improved readability of your code. Check out our built in code checker using pep8 coding style at /TestON/bin/codecheck. All of the TestON test follow the pep8 coding style.

Every case results in your test should be asserted at the end of the case using TestON utilities class. There are different kinds of assert: equals,matches,greater,lesser. Equals assert is used most of the time because it is efficient and easy to use. Below is an example of assert in case 10 of:

Code Block

SAMPstartTemplate2SAMPstartTemplate_1node.py.
main.step( "Start ONOS cluster with basic (drivers) app.")
onosClusterIPs = []
for n in range( 1, numNodes + 1 ):
    handle = "main.ONOScli" + str( n )
    onosClusterIPs.append( eval( handle ).ip_address )

stepResult = main.ONOSbench.startBasicONOS(nodeList = onosClusterIPs, opSleep = 200 )
utilities.assert_equals( expect=main.TRUE,
                         actual=stepResult,
                         onpass="Successfully started basic ONOS cluster ",
                         onfail="Failed to start basic ONOS Cluster " )

...

Page tree

Versions Compared

Old Version 18

New Version 19

Key

SAMPstartTemplate_1node and

SAMPstartTemplate_3node tests

Params File

Topo File