creating a new test suite to find out maximum number of switches connected
authorPeter Gubka <pgubka@cisco.com>
Fri, 19 Jun 2015 23:19:16 +0000 (01:19 +0200)
committerGerrit Code Review <gerrit@opendaylight.org>
Mon, 29 Jun 2015 16:40:22 +0000 (16:40 +0000)
commit7046fc9beffa1c94a30cece84597800e17fef037
treeef4260d26d883792b81144adc7594711dc7c0f89
parent32cd2a50ae7464c77ce14a147cf5c6e3f4ecac88
creating a new test suite to find out maximum number of switches connected

the idea is not to start and stop mininet with different paramentes, but to
add (and remove) switches to the running topology

the other idea is to make that test not as long as the one running from
../../../testplans/openflowplugin-scalability-daily.txt (1.5h). The new suite
has to last much less.

Existing testplans were updated to point on certain files, not the whole directory,
so new robot file can be placed there.

Change-Id: Ifc7c9beb103b87d049f112ac57215705b8364412
Signed-off-by: Peter Gubka <pgubka@cisco.com>
test/csit/libraries/DynamicMininet.py [new file with mode: 0644]
test/csit/suites/openflowplugin/Maximum_Switches/020__find_max_switches.robot [new file with mode: 0644]
test/csit/testplans/openflowplugin-scalability-daily-lithium-redesign.txt
test/csit/testplans/openflowplugin-scalability-daily.txt
test/csit/testplans/openflowplugin-sw-scalability-daily-lithium-redesign.txt [new file with mode: 0644]
test/csit/testplans/openflowplugin-sw-scalability-daily.txt [new file with mode: 0644]