4a45f7dd49
Several tests did not use test_expect_success for their setup commands. Putting these start commands into the testing framework means both that errors during setup will be caught quickly and that non-error text will be suppressed without -v. Signed-off-by: Brian Gernhardt <brian@gernhardtsoftware.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
30 lines
706 B
Bash
Executable File
30 lines
706 B
Bash
Executable File
#!/bin/sh
|
|
#
|
|
# Copyright (c) 2006 Carl D. Worth
|
|
#
|
|
|
|
test_description='git ls-files test for --error-unmatch option
|
|
|
|
This test runs git ls-files --error-unmatch to ensure it correctly
|
|
returns an error when a non-existent path is provided on the command
|
|
line.
|
|
'
|
|
. ./test-lib.sh
|
|
|
|
test_expect_success 'setup' '
|
|
touch foo bar &&
|
|
git update-index --add foo bar &&
|
|
git commit -m "add foo bar"
|
|
'
|
|
|
|
test_expect_success \
|
|
'git ls-files --error-unmatch should fail with unmatched path.' \
|
|
'test_must_fail git ls-files --error-unmatch foo bar-does-not-match'
|
|
|
|
test_expect_success \
|
|
'git ls-files --error-unmatch should succeed eith matched paths.' \
|
|
'git ls-files --error-unmatch foo bar'
|
|
|
|
test_done
|
|
1
|