[ovirt-devel] [Devel] Vdsm functional tests

[Michal Skrivanek]

On Apr 10, 2014, at 06:37 , Vered Volansky <vered at redhat.com> wrote:

> 
> 
> ----- 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?

virt tests are running
There is a common initialization issue with VdsProxy at the moment, once it's fixed the virt tests can be un-silenced and they will hopefully come out of "failing-only" mode:)
I'd say end of this week...

Thanks,
michal

>> 
>> 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