On Wed, Apr 25, 2012 at 10:26:56AM +0200, Lennart Poettering wrote: > On Tue, 24.04.12 21:47, David Strauss (da...@davidstrauss.net) wrote: > > > https://plus.google.com/115547683951727699051/posts/JCDko6rkic5 > > systemd: 20 test tools, Upstart: 17 test tools. > > That said, we always can use more tests (and 20 is not much). We could > use more tests both integrated in the build system (make check), and outside > of > it. The thing about an init systems that is different from many other > software systems is that you can hardly test them entirely > "off-line". To make these tests useful we should actually boot up a full > machine and check if that's entirely clean. > > The ChromeOS folks have an infrastructure that automatically puts > together a VM image every time something is commited, then boots it, > does some checks that things works, measures a couple of performance > parameters (like bootup time) and makes all that available on some web > thingy (including graphs showing how boot-up time improve/regress over > time). I do believe that this kind of infrastructure would be fantastic > to have for systemd too. it probably could be done with a bit of > scripting and not too much work with "yum --installroot", genext2fs, and > qemu-kvm. (alternatively: debootstrap)
Such kind of infrastructure already exists - see os-autoinst [1]. Atm it's used primary by openQA [2] of openSUSE project to test our Factory, but main page claims a support for other distributions as well. [1] http://www.os-autoinst.org/ [2] http://openqa.opensuse.org/ Regards Michal Vyskocil _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
