----- Original Message -----

From: "Dan Kenigsberg" <danken@redhat.com> To: devel@ovirt.org Cc: vdsm-devel@ovirt.org, vered@redhat.com, dougsland@redhat.com, fromani@redhat.com, asegurap@redhat.com Sent: Thursday, April 3, 2014 6: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

Yeah, well, you know it's me... Status haven't changed, working on other urgent stuff right now, can't give an estimate since things pop up. It is very high on the list though. Will let you know when I'm back exclusively on this.

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