On Tue, Oct 21, 2014 at 07:09:14PM +0200, Pino Toscano wrote:
A possible idea just came into my mind is installing the current tests, like: installedtestsdir = $(libdir)/guestfs/tests/somesubdir installedtests_SCRIPTS = $(TESTS) at the bottom of each Makefile.am providing tests, maybe automating that using a small make function; this could make sure all the tests in each directory get installed properly, without moving the logic away from the build system. Regarding the "how to find tests": maybe it is a waste, but an idea could be add, next to test.sh, a test.sh.testinfo (or whatever), in plain text format, with entries like: [Test] Need=appliance,fake-guests CompatSkip=SKIP_OLD_NAME (we have a .ini parser in virt-builder, so that comes for free.) For example, the runner could get a parameter to know whether the appliance has been enabled, and not run tests with "appliance" in Need key. The bigger drawback is that even the tests with nothing to specify in such .testinfo file would need one, even if just with an empty [Test] section.
I was trying to avoid defining another source for generated files, on the general principle that everything that is generated come from one place (in the directory generator/). Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-df lists disk usage of guests without needing to install any software inside the virtual machine. Supports Linux and Windows. http://people.redhat.com/~rjones/virt-df/