git-commit-vandalism/t/t2010-update-cache-badpath.sh
Petr Baudis f50c9f76ca Rename some test scripts and describe the naming convention
First digit: "family", e.g. the absolute basics and global stuff (0),
the basic db-side commands (read-tree, write-tree, commit-tree), the
basic working-tree-side commands (checkout-cache, update-cache), the
other basic commands (ls-files), the diff commands, the pull commands,
exporting commands, revision tree commands...

Second digit: the particular command we are testing

Third digit: (optionally) the particular switch or group of switches
we are testing

Freeform part: commandname-details

Described in the README.

	mv t1000-checkout-cache.sh t2000-checkout-cache-clash.sh
	mv t1001-checkout-cache.sh t2001-checkout-cache-clash.sh
	mv t0200-update-cache.sh t2010-update-cache-badpath.sh
	mv t0400-ls-files.sh t3000-ls-files-others.sh
	mv t0500-ls-files.sh t3010-ls-files-killed.sh
2005-05-15 01:34:22 +02:00

52 lines
1.0 KiB
Bash
Executable File

#!/bin/sh
#
# Copyright (c) 2005 Junio C Hamano
#
test_description='git-update-cache nonsense-path test.
This test creates the following structure in the cache:
path0 - a file
path1 - a symlink
path2/file2 - a file in a directory
path3/file3 - a file in a directory
and tries to git-update-cache --add the following:
path0/file0 - a file in a directory
path1/file1 - a file in a directory
path2 - a file
path3 - a symlink
All of the attempts should fail.
'
. ./test-lib.sh
mkdir path2 path3
date >path0
ln -s xyzzy path1
date >path2/file2
date >path3/file3
test_expect_success \
'git-update-cache --add to add various paths.' \
'git-update-cache --add -- path0 path1 path2/file2 path3/file3'
rm -fr path?
mkdir path0 path1
date >path2
ln -s frotz path3
date >path0/file0
date >path1/file1
for p in path0/file0 path1/file1 path2 path3
do
test_expect_failure \
"git-update-cache to add conflicting path $p should fail." \
"git-update-cache --add -- $p"
done
test_done