[Top][All Lists]

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

Re: Running tests as a gnulib developer

From: Reuben Thomas
Subject: Re: Running tests as a gnulib developer
Date: Tue, 10 Jan 2012 16:55:04 +0000

On 10 January 2012 16:51, Eric Blake <address@hidden> wrote:
> On 01/10/2012 09:30 AM, Reuben Thomas wrote:
>> I've just spent a while trying to work out how to run tests for a
>> particular module, and I'm not getting very far.
>> ./gnulib-tool --help brings up the "--test" mode, which looks
>> promising, but if I run
>> ./gnulib-tool --test --test-dir=/tmp/testdir copy-file
> 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?


reply via email to

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