On Wed, Feb 26, 2014 at 11:12:50PM +0100, Miloslav Trmač wrote:
2014-02-26 22:53 GMT+01:00 Richard W.M. Jones
<rjones(a)redhat.com>:
> But bugs which break the boot prevent you from testing everything else.
>
Only if I would reboot boot my primary workstation into the new untested
software, which I don't do.
Sure, there's the kernel and the graphics drivers and the like which need
physical hardware and booting, but these are the rare exceptions within the
package universe.
As for the case that "I need to reboot so that the gtk2 test suite catches
glib2 bugs", most of these cases are missing tests in glib2. Yes, the
final reboot and re-running all individual test suites in the new
environment might be useful, if there is time and capacity to do such a
test, but it shouldn't be the primary execution mode of the tests; it's too
costly and unfocused, and too far removed from the programmer in the
think/edit/build/test cycle.
I think you may be missing a point here. We're talking about
automated regression testing. The entire stack is tested "all-up" (to
use the Apollo phrase), automatically, in a virtual machine. It
happens without human intervention and (in the os-tree case) in many
thousands of different configurations.
Rich.
--
Richard Jones, Virtualization Group, Red Hat
http://people.redhat.com/~rjones
virt-top is 'top' for virtual machines. Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://people.redhat.com/~rjones/virt-top