[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 17:04:59 +0000

On 10 January 2012 16:58, Eric Blake <address@hidden> wrote:
> Yes, --dir is optional if you don't specify --create-testdir.

Right, so could you please fix the documentation accordingly?
Correcting the help of gnulib-tool seems to be sufficient, since the
--test option is not documented in the manual (at least, I get only
two hits in the manual for "--test", both of which are for
"--test-base"). Adding square brackets around --dir and indicating
that the default is to create a temporary directory in the current
directory (AFAICT from watching it) would be enough.

> 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.

As I explained earlier, that's false: if I do

./gnulib-tool --test copy-file-tests

then the tests are built but not run.


reply via email to

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