2018-04-24 08:08:58 +08:00
|
|
|
#!/bin/sh
|
|
|
|
|
|
|
|
test_description='colored git blame'
|
2020-11-19 07:44:41 +08:00
|
|
|
GIT_TEST_DEFAULT_INITIAL_BRANCH_NAME=main
|
tests: mark tests relying on the current default for `init.defaultBranch`
In addition to the manual adjustment to let the `linux-gcc` CI job run
the test suite with `master` and then with `main`, this patch makes sure
that GIT_TEST_DEFAULT_INITIAL_BRANCH_NAME is set in all test scripts
that currently rely on the initial branch name being `master by default.
To determine which test scripts to mark up, the first step was to
force-set the default branch name to `master` in
- all test scripts that contain the keyword `master`,
- t4211, which expects `t/t4211/history.export` with a hard-coded ref to
initialize the default branch,
- t5560 because it sources `t/t556x_common` which uses `master`,
- t8002 and t8012 because both source `t/annotate-tests.sh` which also
uses `master`)
This trick was performed by this command:
$ sed -i '/^ *\. \.\/\(test-lib\|lib-\(bash\|cvs\|git-svn\)\|gitweb-lib\)\.sh$/i\
GIT_TEST_DEFAULT_INITIAL_BRANCH_NAME=master\
export GIT_TEST_DEFAULT_INITIAL_BRANCH_NAME\
' $(git grep -l master t/t[0-9]*.sh) \
t/t4211*.sh t/t5560*.sh t/t8002*.sh t/t8012*.sh
After that, careful, manual inspection revealed that some of the test
scripts containing the needle `master` do not actually rely on a
specific default branch name: either they mention `master` only in a
comment, or they initialize that branch specificially, or they do not
actually refer to the current default branch. Therefore, the
aforementioned modification was undone in those test scripts thusly:
$ git checkout HEAD -- \
t/t0027-auto-crlf.sh t/t0060-path-utils.sh \
t/t1011-read-tree-sparse-checkout.sh \
t/t1305-config-include.sh t/t1309-early-config.sh \
t/t1402-check-ref-format.sh t/t1450-fsck.sh \
t/t2024-checkout-dwim.sh \
t/t2106-update-index-assume-unchanged.sh \
t/t3040-subprojects-basic.sh t/t3301-notes.sh \
t/t3308-notes-merge.sh t/t3423-rebase-reword.sh \
t/t3436-rebase-more-options.sh \
t/t4015-diff-whitespace.sh t/t4257-am-interactive.sh \
t/t5323-pack-redundant.sh t/t5401-update-hooks.sh \
t/t5511-refspec.sh t/t5526-fetch-submodules.sh \
t/t5529-push-errors.sh t/t5530-upload-pack-error.sh \
t/t5548-push-porcelain.sh \
t/t5552-skipping-fetch-negotiator.sh \
t/t5572-pull-submodule.sh t/t5608-clone-2gb.sh \
t/t5614-clone-submodules-shallow.sh \
t/t7508-status.sh t/t7606-merge-custom.sh \
t/t9302-fast-import-unpack-limit.sh
We excluded one set of test scripts in these commands, though: the range
of `git p4` tests. The reason? `git p4` stores the (foreign) remote
branch in the branch called `p4/master`, which is obviously not the
default branch. Manual analysis revealed that only five of these tests
actually require a specific default branch name to pass; They were
modified thusly:
$ sed -i '/^ *\. \.\/lib-git-p4\.sh$/i\
GIT_TEST_DEFAULT_INITIAL_BRANCH_NAME=master\
export GIT_TEST_DEFAULT_INITIAL_BRANCH_NAME\
' t/t980[0167]*.sh t/t9811*.sh
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2020-11-19 07:44:19 +08:00
|
|
|
export GIT_TEST_DEFAULT_INITIAL_BRANCH_NAME
|
|
|
|
|
2018-04-24 08:08:58 +08:00
|
|
|
. ./test-lib.sh
|
|
|
|
|
|
|
|
PROG='git blame -c'
|
|
|
|
. "$TEST_DIRECTORY"/annotate-tests.sh
|
|
|
|
|
|
|
|
test_expect_success 'colored blame colors contiguous lines' '
|
|
|
|
git -c color.blame.repeatedLines=yellow blame --color-lines --abbrev=12 hello.c >actual.raw &&
|
2018-04-24 08:09:00 +08:00
|
|
|
git -c color.blame.repeatedLines=yellow -c blame.coloring=repeatedLines blame --abbrev=12 hello.c >actual.raw.2 &&
|
|
|
|
test_cmp actual.raw actual.raw.2 &&
|
2018-04-24 08:08:58 +08:00
|
|
|
test_decode_color <actual.raw >actual &&
|
|
|
|
grep "<YELLOW>" <actual >darkened &&
|
|
|
|
grep "(F" darkened > F.expect &&
|
|
|
|
grep "(H" darkened > H.expect &&
|
|
|
|
test_line_count = 2 F.expect &&
|
|
|
|
test_line_count = 3 H.expect
|
|
|
|
'
|
|
|
|
|
2018-04-24 08:08:59 +08:00
|
|
|
test_expect_success 'color by age consistently colors old code' '
|
|
|
|
git blame --color-by-age hello.c >actual.raw &&
|
2018-04-24 08:09:00 +08:00
|
|
|
git -c blame.coloring=highlightRecent blame hello.c >actual.raw.2 &&
|
|
|
|
test_cmp actual.raw actual.raw.2 &&
|
2018-04-24 08:08:59 +08:00
|
|
|
test_decode_color <actual.raw >actual &&
|
|
|
|
grep "<BLUE>" <actual >colored &&
|
|
|
|
test_line_count = 10 colored
|
|
|
|
'
|
|
|
|
|
|
|
|
test_expect_success 'blame color by age: new code is different' '
|
|
|
|
cat >>hello.c <<-EOF &&
|
|
|
|
void qfunc();
|
|
|
|
EOF
|
|
|
|
git add hello.c &&
|
|
|
|
GIT_AUTHOR_DATE="" git commit -m "new commit" &&
|
|
|
|
|
|
|
|
git -c color.blame.highlightRecent="yellow,1 month ago, cyan" blame --color-by-age hello.c >actual.raw &&
|
|
|
|
test_decode_color <actual.raw >actual &&
|
|
|
|
|
|
|
|
grep "<YELLOW>" <actual >colored &&
|
|
|
|
test_line_count = 10 colored &&
|
|
|
|
|
|
|
|
grep "<CYAN>" <actual >colored &&
|
|
|
|
test_line_count = 1 colored &&
|
|
|
|
grep qfunc colored
|
|
|
|
'
|
|
|
|
|
2018-04-24 08:08:58 +08:00
|
|
|
test_done
|