[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Running tests as a gnulib developer

From: Eric Blake
Subject: Re: Running tests as a gnulib developer
Date: Tue, 10 Jan 2012 09:58:37 -0700
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:9.0) Gecko/20111222 Thunderbird/9.0

On 01/10/2012 09:55 AM, Reuben Thomas wrote:
>> That says where the test dir should be located, but didn't load any test
>> modules to actually do the testing.  Personally, I use:
>> ./gnulib-tool --with-tests --test copy-file
>> which says to include the copy-file-tests module automatically, as well
>> as running the unit test (and clean it up on success), when developing
>> on a single machine.
> The syntax summary of gnulib-tool:
>        gnulib-tool --test --dir=directory module1 ... moduleN
> says that the --dir argument is mandatory. (Sorry, I wrote --test-dir
> in my examples; that should've been --dir.) From what you say above,
> the --dir argument has a default value?

Yes, --dir is optional if you don't specify --create-testdir.  Likewise,
--with-tests is important if you want all associated unit tests;
otherwise, your moduleN list has to manually include just the
module-tests modules that you want to run.

Eric Blake   address@hidden    +1-919-301-3266
Libvirt virtualization library http://libvirt.org

Attachment: signature.asc
Description: OpenPGP digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]