On Fri, Mar 17, 2017, at 11:00 PM, Dusty Mabe wrote: > > Yes! we would love a UEFI test
Yes; conceptually most of the important scenarios we run through for Workstation/Server (e.g. dm-crypt versus not) we should also do for Atomic Host. Adam, where is the git containing the input test suite for OpenQA? > and I think it would actually be good > to run the atomic-host-tests against these images assuming openQA is > the right tool for that job. This part I don't quite agree with - remember the cloud images are built with the installer ISO, and *those* are tested already with a-h-t. There's going to be very little that's specific to the ISO path versus the cloud image - which is part of the whole idea of sharing the same exact ostree commit across them. > I thought openQA was more for interactive > install testing, It does do more than that - however I see it as mostly valuable for testing interactive Anaconda runs with the OpenCV approach. IMO OpenQA's use of OpenCV is less interesting for testing "headless/non-GUI" bits, as is the case for Atomic Host. (We do of course have Cockpit and the OpenShift web console, but both of those use Selenium[1][2] already) [1] https://github.com/cockpit-project/cockpit/blob/master/test/avocado/selenium-base.py [2] https://github.com/openshift/origin-web-console/blob/master/package.json#L64 _______________________________________________ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
