On Fri, Jun 28, 2013 at 7:04 AM, Stefan Stanacar
<stefanx.stanacar@intel.com> wrote:
...
> There are some areas for improvement/limitations right now:> - a better way of getting the list of installed packages in a image> - qemu is started with the -snapshot option, we should create a copy of the original rootfs instead.> - when using TEST_SUITES = "auto" there is no dependency at all between tests (rpm would run before ssh test), so better use TEST_SUITES = "ping ssh auto"> - better logging and error reporting for qemu problems (runqemu erros, qemu doesn't start, etc)> - more helper methods for tests> - others I can't think of right now :)
Did you think about adding something like an overidable set of hooks
which starts, setup image and shutdown the machine? This would allow
same framework to be used for real hardware test.
Regards,
--
Otavio Salvador O.S. Systems
http://www.ossystems.com.br http://projetos.ossystems.com.br
Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750

On Friday 28 June 2013 19:06:04 Otavio Salvador wrote:
> Did you think about adding something like an overidable set of hooks> which starts, setup image and shutdown the machine? This would allow> same framework to be used for real hardware test.
Yes, we did think about this; the way this would be done would be to simply
swap out the QemuRunner instance at runtime with some other class that has the
same interface which would provision a real machine. However there is no
established framework for doing the latter, and at the moment we just want to
concentrate on getting runtime tests working. As long as the tests themselves
know as little as possible about the machine they are running in then
switching over to real hardware is pretty straightforward, and we've tried to
design things in that manner.
Cheers,
Paul