mirror of
https://github.com/git/git.git
synced 2024-11-30 21:44:02 +08:00
describe tests: improve test for --work-tree & --dirty
Improve tests added in9f67d2e827
(Teach "git describe" --dirty option, 2009-10-21) and2ed5c8e174
(describe: setup working tree for --dirty, 2019-02-03) so that they make sense in combination with each other. The "check_describe" being removed here was the earlier test, we then later added these --work-tree tests which really just wanted to check if we got the exact same output from "describe", but the test wasn't structured to test for that. Let's change it to do that, which both improves test coverage and makes it more obvious what's going on here. Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:
parent
f0d4d398e2
commit
2df546e17f
@ -151,24 +151,24 @@ test_expect_success 'set-up dirty work tree' '
|
||||
echo >>file
|
||||
'
|
||||
|
||||
check_describe "A-*[0-9a-f]-dirty" --dirty
|
||||
|
||||
test_expect_success 'describe --dirty with --work-tree (dirty)' '
|
||||
git describe --dirty >expected &&
|
||||
(
|
||||
cd "$TEST_DIRECTORY" &&
|
||||
git --git-dir "$TRASH_DIRECTORY/.git" --work-tree "$TRASH_DIRECTORY" describe --dirty >"$TRASH_DIRECTORY/out"
|
||||
) &&
|
||||
grep -E "^A-[1-9][0-9]?-g[0-9a-f]+-dirty$" out
|
||||
grep -E "^A-[1-9][0-9]?-g[0-9a-f]+-dirty$" out &&
|
||||
test_cmp expected out
|
||||
'
|
||||
|
||||
check_describe "A-*[0-9a-f].mod" --dirty=.mod
|
||||
|
||||
test_expect_success 'describe --dirty=.mod with --work-tree (dirty)' '
|
||||
git describe --dirty=.mod >expected &&
|
||||
(
|
||||
cd "$TEST_DIRECTORY" &&
|
||||
git --git-dir "$TRASH_DIRECTORY/.git" --work-tree "$TRASH_DIRECTORY" describe --dirty=.mod >"$TRASH_DIRECTORY/out"
|
||||
) &&
|
||||
grep -E "^A-[1-9][0-9]?-g[0-9a-f]+.mod$" out
|
||||
grep -E "^A-[1-9][0-9]?-g[0-9a-f]+.mod$" out &&
|
||||
test_cmp expected out
|
||||
'
|
||||
|
||||
test_expect_success 'describe --dirty HEAD' '
|
||||
|
Loading…
Reference in New Issue
Block a user