For example, in tests/dpif-netdev.at file, there are OVS_VSWITCHD_START( > [add-port br0 p1 -- set interface p1 type=dummy > options:pstream=punix:$OVS_RUNDIR/p0.sock ofport_request=1 -- \ > add-port br0 p7 -- set interface p7 ofport_request=7 type=dummy -- \ > add-br br1 -- \ > set bridge br1 other-config:hwaddr=aa:66:aa:66:00:00 -- \ > set bridge br1 datapath-type=dummy other-config:datapath-id=1234 \ > fail-mode=secure -- \ > add-port br1 p2 -- set interface p2 type=dummy > options:stream=unix:$OVS_RUNDIR/p0.sock ofport_request=2 -- \ > add-port br1 p8 -- set interface p8 ofport_request=8 type=dummy --])
if no vswitchd started, `add-port` will failed. 2017-08-08 10:03 GMT+08:00 Sam <[email protected]>: > Hi all, > > I'm working on ovs tests, and I want to add my test, so I have few > questions: > > 1. what testing frame work does ovs-tests use, as I have seen lots of *.at > file, lots of AT_*() macro. > > 2. Will ovs-tests start ovs-vswitchd or ovsdb-server when running test by > `make check` command? As if no vswitchd started, how to test it? > > 3. Also there are *.py files, how it works? > > Thank you~ > _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
