[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Running tests as a gnulib developer
From: |
Bruno Haible |
Subject: |
Re: Running tests as a gnulib developer |
Date: |
Tue, 10 Jan 2012 20:56:30 +0100 |
User-agent: |
KMail/4.7.4 (Linux/3.1.0-1.2-desktop; KDE/4.7.4; x86_64; ; ) |
Reuben Thomas wrote:
> Oh wait…
>
> ./gnulib-tool --test --dir=/tmp/testdir --with-tests copy-file-tests
>
> seems to do what I want! Still, this is not exactly obvious.
Hope this patch will make it a little bit more obvious.
2012-01-10 Bruno Haible <address@hidden>
doc: Mention --with-tests option.
* gnulib-tool (func_usage): Suggest --with-tests for --test etc.
* doc/gnulib.texi (Extra tests modules): Mention the need to pass
--with-tests.
Reported by Reuben Thomas.
diff --git a/doc/gnulib.texi b/doc/gnulib.texi
index 8363202..1ab056f 100644
--- a/doc/gnulib.texi
+++ b/doc/gnulib.texi
@@ -825,17 +825,17 @@ there is no workaround about it. Such a test is better
avoided in a
release that is made for the general public.
@end table
address@hidden --import} will not include tests marked with these
-attributes by default. When @code{gnulib-tool} is invoked with one
address@hidden --import --with-tests} will not include tests marked with
+these attributes by default. When @code{gnulib-tool} is invoked with one
of the options @code{--with-c++-tests}, @code{--with-longrunning-tests},
@code{--with-privileged-tests}, @code{--with-unportable-tests}, it
will include tests despite the corresponding special status attribute.
When @code{gnulib-tool} receives the option @code{--with-all-tests},
it will include all tests regardless of their status attributes.
address@hidden --create-testdir} and
address@hidden --create-megatestdir} by default include all tests of
-modules specified on the command line, regardless of their status
address@hidden --create-testdir --with-tests} and
address@hidden --create-megatestdir --with-tests} by default include all
+tests of modules specified on the command line, regardless of their status
attributes. Tests of modules occurring as dependencies are not included
by default if they have one of these status attributes. The options
@code{--with-c++-tests}, @code{--with-longrunning-tests},
diff --git a/gnulib-tool b/gnulib-tool
index da3aa4d..de8f6fe 100755
--- a/gnulib-tool
+++ b/gnulib-tool
@@ -164,11 +164,15 @@ Operation modes:
--update update the current package, restore files omitted
from version control
--create-testdir create a scratch package with the given modules
+ (pass --with-tests to include the unit tests)
--create-megatestdir create a mega scratch package with the given
modules
one by one and all together
+ (pass --with-tests to include the unit tests)
--test test the combination of the given modules
+ (pass --with-tests to include the unit tests)
(recommended to use CC=\"gcc -Wall\" here)
--megatest test the given modules one by one and all together
+ (pass --with-tests to include the unit tests)
(recommended to use CC=\"gcc -Wall\" here)
--extract-description extract the description
--extract-comment extract the comment
Re: Running tests as a gnulib developer, Bruno Haible, 2012/01/10
Re: Running tests as a gnulib developer,
Bruno Haible <=