Daniel P. Berrange wrote: > On Tue, May 11, 2010 at 10:02:01PM +0200, Jim Meyering wrote: ... >> However, a test that's skipped whenever it detects a running >> libvirtd is less valuable than one that runs unconditionally, >> so libvirt-tck is probably the ideal destination. >> >> It is critically important to have an easily accessible "make check"- >> like process that can be used to exercise more of libvirt. >> I hope libvirt-tck will soon fit the bill. > > It already fits that bill & is catching & preventing significant bugs in > QEMU. It has been invaluable in porting libvirt to the new QEMU JSON > interface for command & control - it wouldn't have been practical without > it in fact. Didn't mean to impugn libvirt-tck. On the contrary, it looks great. It's just that we need a way to be able to run -- quickly and conveniently -- "make check"-style tests, including integration tests. -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list