Re: [ovirt-devel] hosted-engine ovirt-system-tests

On Mon, Mar 5, 2018 at 3:01 PM, Yedidyah Bar David <didi(a)redhat.com&gt; wrote: I'll answer generally, since specifically for each test we'll need to see. The guidelines that I have (in my head, not written down anywhere) are really: 1. Be efficient in resource - HW mainly. My guideline is quite simple - can it run on my laptop (8GB of RAM). Not everything can fit of course on my laptop (the performance suite, the upcoming OpenShift on oVirt suite, etc.), but I try. 2. Be quick - whatever we can test in parallel to other tests, is much preferred. We have quite a bit of 'dead time' between tests, we need to use them. 3. Bend the rules, but don't cheat - I move the yum cache repo to /dev/shm, etc. - to make things quicker, but I don't cheat and install deps. ahead of time, etc. 4. Most suites do not run too often (several times a day) - I think it's OK to add to those that run once a day or so. 5. Strive for others (QE!) to contribute to the suite. The more we can collaborate, the better. 6. Generally, we have enough gaps in our positive tests, that I rather not introduce negative tests. 7. Whatever we can do in order to ensure QE does not get a dead-on-arrival or broken functionality build - the better. Bugzilla, but I did not see anything there for quite some time. Many of those change the default installation and test the 'interesting' combinations - which I think is great. I'd be happy for a setup with custom '3rd party' certificate, Kerberos auth., ovirtmgmt on a VLAN interface, etc. Y.