Merge with gitk --parents change.

[git.git] / t / README

diff --git a/t/README b/t/README
index 146e261..ab47ef9 100644 (file)
--- a/t/README
+++ b/t/README
@@ -32,7 +32,7 @@ the tests.
 Or you can run each test individually from command line, like
 this:
 
 Or you can run each test individually from command line, like
 this:
 

-    $ sh ./t0500-ls-files.sh
+    $ sh ./t3001-ls-files-killed.sh

     *   ok 1: git-update-cache --add to add various paths.
     *   ok 2: git-ls-files -k to show killed files.
     *   ok 3: validate git-ls-files -k output.
     *   ok 1: git-update-cache --add to add various paths.
     *   ok 2: git-ls-files -k to show killed files.
     *   ok 3: validate git-ls-files -k output.


@@ -79,6 +79,14 @@ Second digit tells the particular command we are testing.
 Third digit (optionally) tells the particular switch or group of switches
 we are testing.
 
 Third digit (optionally) tells the particular switch or group of switches
 we are testing.
 

+If you create files under t/ directory (i.e. here) that is not
+the top-level test script, never name the file to match the above
+pattern.  The Makefile here considers all such files as the
+top-level test script and tries to run all of them.  A care is
+especially needed if you are creating a common test library
+file, similar to test-lib.sh, because such a library file may
+not be suitable for standalone execution.
+

 
 Writing Tests
 -------------
 
 Writing Tests
 -------------


@@ -92,7 +100,7 @@ assignment to variable 'test_description', like this:
        # Copyright (c) 2005 Junio C Hamano
        #
 
        # Copyright (c) 2005 Junio C Hamano
        #
 

-       test_description=xxx test (option --frotz)
+       test_description='xxx test (option --frotz)

 
        This test registers the following structure in the cache
        and tries to run git-ls-files with option --frotz.'
 
        This test registers the following structure in the cache
        and tries to run git-ls-files with option --frotz.'


@@ -120,6 +128,7 @@ This test harness library does the following things:
    consistently when command line arguments --verbose (or -v),
    --debug (or -d), and --immediate (or -i) is given.
 
    consistently when command line arguments --verbose (or -v),
    --debug (or -d), and --immediate (or -i) is given.
 

+

 End with test_done
 ------------------
 
 End with test_done
 ------------------