The documentation of the test harness still refer to old
numbering and also contains an obvious typo.
Also "make test" should be run after making sure we have built
all binaries, since test is designed to test the newly built
ones.
Signed-off-by: Junio C Hamano <junkio@cox.net>
Signed-off-by: Petr Baudis <pasky@ucw.cz>
strbuf.o: $(LIB_H)
gitenv.o: $(LIB_H)
strbuf.o: $(LIB_H)
gitenv.o: $(LIB_H)
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.
# 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.'
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
------------------