----- Original Message ----- > From: "Dan Kenigsberg" <[email protected]> > To: [email protected] > Cc: [email protected], [email protected], [email protected], > [email protected], [email protected] > Sent: Thursday, April 3, 2014 5:08:31 PM > Subject: Vdsm functional tests > > Functional tests are intended to verify that a running Vdsm instance > does what it should, when treated as a black box, over its public API. > > They should be comprehensive and representative of a typical field usage > of Vdsm. It is a sin to break such a test - but we must be able to know > when such a sin is committed. > > We currently have the following functional tests modules: > > - sosPluginTests.py > supervdsmFuncTests.py > > - storageTests.py > > - momTests.py > virtTests.py > > - networkTests.py > > I'd like to have a designated developer per team (infra, storage, virt and > network), responsible to having these tests ever-running.
I'm already serving the networkTests.py cause and will continue to do so. > > When could we expect to have it running per commit on a Jenkins slaves? Done for networkTests.py (branches ovirt-3.4 and master). If any other team needs help with setting this up, just let me know. > > Volunteers, please come forward. > > Dan. > _______________________________________________ Devel mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/devel
