----- Original Message ----- > From: "Francesco Romani" <[email protected]> > To: "Dan Kenigsberg" <[email protected]> > Cc: [email protected], [email protected], [email protected], > [email protected], [email protected] > Sent: Thursday, April 3, 2014 5:25:41 PM > Subject: Re: Vdsm functional tests > > ----- 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. > [...] > > I'd like to have a designated developer per team (infra, storage, virt and > > network), responsible to having these tests ever-running. > > Count on me for this. > > > When could we expect to have it running per commit on a Jenkins slaves? > > I know virt functional tests arent' comprehensive and can be improved, but > I'm not aware of any major drawback about them (e.g. unbearable slowness, > resource leak...). Am I missing something big here?
Well, in order to activate them we should have them consistently passing on master/ovirt-3.4 to know that they are not broken. If that is the case. Let's work in making the jenkins job. > > > -- > Francesco Romani > RedHat Engineering Virtualization R & D > Phone: 8261328 > IRC: fromani > _______________________________________________ Devel mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/devel
