> It would be a lot easier to release a new version of sysvinit if we > had a test suite testing that the system work. At the moment, I am > unsure if the system work at all until I try to boot with it, and that > is a some work to set up. > > If we had a simple 'make check' target running a test suite, I would > be less relucant to make new releases. > > Anyone got a good idea how to create such test suite? >
Probably the test suite can consist in a tiny embedded system, and qemu used to boot the system. I also think it would be wise to post a release candidate before the final version.