login: add support for directories in MOTD_FILE=

[thirdparty/util-linux.git] / Documentation / howto-tests.txt

diff --git a/Documentation/howto-tests.txt b/Documentation/howto-tests.txt
index 71c7f85c1612719c82954fc136387c71e45ddfbd..b8a6200732660e30277ce740046b36bc3ea5b671 100644 (file)
--- a/Documentation/howto-tests.txt
+++ b/Documentation/howto-tests.txt
@@ -5,21 +5,25 @@
  It's expected that for each invasive change or important bugfix you will
  include a test to your patch.
 
- Compile tests & run basic tests:
+ Compile binaries, libs, extra test programs and run the basic tests:
 
        $ make check
 
+ Compile extra test programs only:
+
+       $ make check-programs
+
  Note that the configure option --disable-static disables many of libmount and
  libblkid unit tests.
 
  Run all tests including tests that require root permissions:
 
        # cd tests
-       # ./run.sh [--verbose] [--memcheck]
+       # ./run.sh [options, see --help]
 
        Alternatively using sudo and make:
 
-       $ make check TS_COMMAND="true"
+       $ make check-programs
        $ sudo -E make check TS_OPTS="--parallel=1"
 
  note that as root you have to manually remove output and diff directories
@@ -31,6 +35,7 @@
 
  Run subset of tests:
 
+       $ cd tests
        $ ./run.sh <test_directory-name>
 
         for example:
@@ -38,6 +43,10 @@
               $ ./run.sh blkid
               $ ./run.sh libmount
 
+        or individual test script, for example:
+
+             $ ./ts/cal/year
+
  The tests is possible to exclude by ./run.sh --exclude=<list>  where the
  <list> is blank separated test names in format "testdir/testname", for example:
 
@@ -104,7 +113,7 @@ TS_OPT_testdir_[testscript_]memcheck="<yes|no>"
     Run certain tests with valgrind. Similar usage like TS_OPT_*_fake above.
 
 
-External services 
+External services
 -----------------
 
 Travis CI - automatically executed for all github commits.
@@ -132,6 +141,6 @@ Drone.io - automatically executed for all github commits.
        ret=0
        travis_script || ret=$?
        travis_after_script
-       exit $ret  
-       
+       exit $ret
+
     yes, it shares the setup functions with travis-ci.