[vdsm] Fwd: [ovirt-devel] [Devel] Vdsm functional tests
Vered Volansky
vered at redhat.com
Thu Apr 10 05:10:41 UTC 2014
----- Forwarded Message -----
> From: "Vered Volansky" <vered at redhat.com>
> To: "Dan Kenigsberg" <danken at redhat.com>
> Cc: vdsm-devel at ovirt.org, devel at ovirt.org
> Sent: Thursday, April 10, 2014 7:37:51 AM
> Subject: Re: [ovirt-devel] [Devel] Vdsm functional tests
>
>
>
> ----- Original Message -----
> > From: "Dan Kenigsberg" <danken at redhat.com>
> > To: devel at ovirt.org
> > Cc: vdsm-devel at ovirt.org, vered at redhat.com, fromani at redhat.com
> > Sent: Thursday, April 3, 2014 6:08:31 PM
> > Subject: [Devel] 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
>
> Storage localfs will be good to go by May 8th.
> >
> > - 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.
> >
> > When could we expect to have it running per commit on a Jenkins slaves?
> >
> > Volunteers, please come forward.
> >
> > Dan.
> > _______________________________________________
> > Devel mailing list
> > Devel at ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/devel
> >
> _______________________________________________
> Devel mailing list
> Devel at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
>
More information about the vdsm-devel
mailing list