Instalatron: Anaconda testing framework
hoyang at redhat.com
Wed Jul 20 09:23:34 UTC 2011
----- Original Message -----
> From: "Sergio Rubio" <rubiojr at frameos.org>
> To: "Eric Blake" <eblake at redhat.com>
> Cc: "For testing and quality assurance of Fedora releases" <test at lists.fedoraproject.org>
> Sent: Wednesday, July 20, 2011 4:17:35 AM
> Subject: Re: Instalatron: Anaconda testing framework
> On Tuesday, July 19, 2011, Eric Blake <eblake at redhat.com> wrote:
> > If that's the only reason, then we should really try to use kvm
> > instead, since qemu-kvm recently learned how to inject arbitrary
> > scancodes, and libvirt 0.9.4 is gaining support for exposing that
> > capability from command line. Fedora gains all around if we exercise
> > our own open virt stack instead of a proprietary one.
> Very reasonable. Thanks for pointing out. Haven't been following
> libvirt/KVM developments lately...
> Abstracting the hypervisor related stuff will be kind of easy I guess.
> > --
> > Eric Blake eblake at redhat.com +1-801-349-2682
> > Libvirt virtualization library http://libvirt.org
> test mailing list
> test at lists.fedoraproject.org
> To unsubscribe:
Thanks for sharing. Now I and Tao Wu are working on the project Fedora installation test automation.
The project is based on the Autotest framework and part of the AutoQA project.
Now it is using qemu-kvm and the test results are read from the logs. The installations from url,
DVD, hard drive and upgrade are almost finished, we try to implement all the tests roughly first, so we can
use them at the usual tests, more details will be done later.
I think we also will adopt screen-shot in future, since we cannot see the errors of UIs from logs.
I saw you compare the images in the codes, but which are images should the screen-shots compare with
when one new product is released?
Thanks again, I leaned much from you codes, You are the first one I meet also works on the installation
test. Glad to know you.
More information about the test