1#!/bin/sh 2# 3# Copyright (c) 2005 Junio C Hamano 4# 5# This program is free software: you can redistribute it and/or modify 6# it under the terms of the GNU General Public License as published by 7# the Free Software Foundation, either version 2 of the License, or 8# (at your option) any later version. 9# 10# This program is distributed in the hope that it will be useful, 11# but WITHOUT ANY WARRANTY; without even the implied warranty of 12# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the 13# GNU General Public License for more details. 14# 15# You should have received a copy of the GNU General Public License 16# along with this program. If not, see http://www.gnu.org/licenses/ . 17 18# The semantics of the editor variables are that of invoking 19# sh -c "$EDITOR \"$@\"" files ... 20# 21# If our trash directory contains shell metacharacters, they will be 22# interpreted if we just set $EDITOR directly, so do a little dance with 23# environment variables to work around this. 24# 25# In particular, quoting isn't enough, as the path may contain the same quote 26# that we're using. 27test_set_editor () { 28 FAKE_EDITOR="$1" 29export FAKE_EDITOR 30 EDITOR='"$FAKE_EDITOR"' 31export EDITOR 32} 33 34test_decode_color () { 35awk' 36 function name(n) { 37 if (n == 0) return "RESET"; 38 if (n == 1) return "BOLD"; 39 if (n == 30) return "BLACK"; 40 if (n == 31) return "RED"; 41 if (n == 32) return "GREEN"; 42 if (n == 33) return "YELLOW"; 43 if (n == 34) return "BLUE"; 44 if (n == 35) return "MAGENTA"; 45 if (n == 36) return "CYAN"; 46 if (n == 37) return "WHITE"; 47 if (n == 40) return "BLACK"; 48 if (n == 41) return "BRED"; 49 if (n == 42) return "BGREEN"; 50 if (n == 43) return "BYELLOW"; 51 if (n == 44) return "BBLUE"; 52 if (n == 45) return "BMAGENTA"; 53 if (n == 46) return "BCYAN"; 54 if (n == 47) return "BWHITE"; 55 } 56 { 57 while (match($0, /\033\[[0-9;]*m/) != 0) { 58 printf "%s<", substr($0, 1, RSTART-1); 59 codes = substr($0, RSTART+2, RLENGTH-3); 60 if (length(codes) == 0) 61 printf "%s", name(0) 62 else { 63 n = split(codes, ary, ";"); 64 sep = ""; 65 for (i = 1; i <= n; i++) { 66 printf "%s%s", sep, name(ary[i]); 67 sep = ";" 68 } 69 } 70 printf ">"; 71$0= substr($0, RSTART + RLENGTH, length($0) - RSTART - RLENGTH + 1); 72 } 73 print 74 } 75 ' 76} 77 78nul_to_q () { 79"$PERL_PATH"-pe'y/\000/Q/' 80} 81 82q_to_nul () { 83"$PERL_PATH"-pe'y/Q/\000/' 84} 85 86q_to_cr () { 87tr Q '\015' 88} 89 90q_to_tab () { 91tr Q '\011' 92} 93 94qz_to_tab_space () { 95tr QZ '\011\040' 96} 97 98append_cr () { 99sed-e's/$/Q/'|tr Q '\015' 100} 101 102remove_cr () { 103tr'\015' Q |sed-e's/Q$//' 104} 105 106# In some bourne shell implementations, the "unset" builtin returns 107# nonzero status when a variable to be unset was not set in the first 108# place. 109# 110# Use sane_unset when that should not be considered an error. 111 112sane_unset () { 113unset"$@" 114return0 115} 116 117test_tick () { 118iftest -z"${test_tick+set}" 119then 120 test_tick=1112911993 121else 122 test_tick=$(($test_tick + 60)) 123fi 124 GIT_COMMITTER_DATE="$test_tick-0700" 125 GIT_AUTHOR_DATE="$test_tick-0700" 126export GIT_COMMITTER_DATE GIT_AUTHOR_DATE 127} 128 129# Stop execution and start a shell. This is useful for debugging tests and 130# only makes sense together with "-v". 131# 132# Be sure to remove all invocations of this command before submitting. 133 134test_pause () { 135iftest"$verbose"= t;then 136"$SHELL_PATH"<&6>&3 2>&4 137else 138 error >&5"test_pause requires --verbose" 139fi 140} 141 142# Call test_commit with the arguments "<message> [<file> [<contents> [<tag>]]]" 143# 144# This will commit a file with the given contents and the given commit 145# message, and tag the resulting commit with the given tag name. 146# 147# <file>, <contents>, and <tag> all default to <message>. 148 149test_commit () { 150 notick= && 151 signoff= && 152whiletest$#!=0 153do 154case"$1"in 155--notick) 156 notick=yes 157;; 158--signoff) 159 signoff="$1" 160;; 161*) 162break 163;; 164esac 165shift 166done&& 167file=${2:-"$1.t"}&& 168echo"${3-$1}">"$file"&& 169 git add "$file"&& 170iftest -z"$notick" 171then 172 test_tick 173fi&& 174 git commit $signoff-m"$1"&& 175 git tag "${4:-$1}" 176} 177 178# Call test_merge with the arguments "<message> <commit>", where <commit> 179# can be a tag pointing to the commit-to-merge. 180 181test_merge () { 182 test_tick && 183 git merge -m"$1""$2"&& 184 git tag "$1" 185} 186 187# This function helps systems where core.filemode=false is set. 188# Use it instead of plain 'chmod +x' to set or unset the executable bit 189# of a file in the working directory and add it to the index. 190 191test_chmod () { 192chmod"$@"&& 193 git update-index --add"--chmod=$@" 194} 195 196# Unset a configuration variable, but don't fail if it doesn't exist. 197test_unconfig () { 198 git config --unset-all"$@" 199 config_status=$? 200case"$config_status"in 2015)# ok, nothing to unset 202 config_status=0 203;; 204esac 205return$config_status 206} 207 208# Set git config, automatically unsetting it after the test is over. 209test_config () { 210 test_when_finished "test_unconfig '$1'"&& 211 git config "$@" 212} 213 214test_config_global () { 215 test_when_finished "test_unconfig --global '$1'"&& 216 git config --global"$@" 217} 218 219write_script () { 220{ 221echo"#!${2-"$SHELL_PATH"}"&& 222cat 223} >"$1"&& 224chmod+x "$1" 225} 226 227# Use test_set_prereq to tell that a particular prerequisite is available. 228# The prerequisite can later be checked for in two ways: 229# 230# - Explicitly using test_have_prereq. 231# 232# - Implicitly by specifying the prerequisite tag in the calls to 233# test_expect_{success,failure,code}. 234# 235# The single parameter is the prerequisite tag (a simple word, in all 236# capital letters by convention). 237 238test_set_prereq () { 239 satisfied_prereq="$satisfied_prereq$1" 240} 241satisfied_prereq=" " 242lazily_testable_prereq= lazily_tested_prereq= 243 244# Usage: test_lazy_prereq PREREQ 'script' 245test_lazy_prereq () { 246 lazily_testable_prereq="$lazily_testable_prereq$1" 247eval test_prereq_lazily_$1=\$2 248} 249 250test_run_lazy_prereq_ () { 251script=' 252mkdir -p "$TRASH_DIRECTORY/prereq-test-dir" && 253( 254 cd "$TRASH_DIRECTORY/prereq-test-dir" &&'"$2"' 255)' 256 say >&3"checking prerequisite:$1" 257 say >&3"$script" 258 test_eval_ "$script" 259 eval_ret=$? 260rm-rf"$TRASH_DIRECTORY/prereq-test-dir" 261iftest"$eval_ret"=0;then 262 say >&3"prerequisite$1ok" 263else 264 say >&3"prerequisite$1not satisfied" 265fi 266return$eval_ret 267} 268 269test_have_prereq () { 270# prerequisites can be concatenated with ',' 271 save_IFS=$IFS 272 IFS=, 273set -- $* 274 IFS=$save_IFS 275 276 total_prereq=0 277 ok_prereq=0 278 missing_prereq= 279 280for prerequisite 281do 282case"$prerequisite"in 283!*) 284 negative_prereq=t 285 prerequisite=${prerequisite#!} 286;; 287*) 288 negative_prereq= 289esac 290 291case"$lazily_tested_prereq"in 292*"$prerequisite"*) 293;; 294*) 295case"$lazily_testable_prereq"in 296*"$prerequisite"*) 297eval"script=\$test_prereq_lazily_$prerequisite"&& 298if test_run_lazy_prereq_ "$prerequisite""$script" 299then 300 test_set_prereq $prerequisite 301fi 302 lazily_tested_prereq="$lazily_tested_prereq$prerequisite" 303esac 304;; 305esac 306 307 total_prereq=$(($total_prereq + 1)) 308case"$satisfied_prereq"in 309*"$prerequisite"*) 310 satisfied_this_prereq=t 311;; 312*) 313 satisfied_this_prereq= 314esac 315 316case"$satisfied_this_prereq,$negative_prereq"in 317 t,|,t) 318 ok_prereq=$(($ok_prereq + 1)) 319;; 320*) 321# Keep a list of missing prerequisites; restore 322# the negative marker if necessary. 323 prerequisite=${negative_prereq:+!}$prerequisite 324iftest -z"$missing_prereq" 325then 326 missing_prereq=$prerequisite 327else 328 missing_prereq="$prerequisite,$missing_prereq" 329fi 330esac 331done 332 333test$total_prereq=$ok_prereq 334} 335 336test_declared_prereq () { 337case",$test_prereq,"in 338*,$1,*) 339return0 340;; 341esac 342return1 343} 344 345test_expect_failure () { 346test"$#"=3&& { test_prereq=$1;shift; } || test_prereq= 347test"$#"=2|| 348 error "bug in the test script: not 2 or 3 parameters to test-expect-failure" 349export test_prereq 350if! test_skip "$@" 351then 352 say >&3"checking known breakage:$2" 353if test_run_ "$2" expecting_failure 354then 355 test_known_broken_ok_ "$1" 356else 357 test_known_broken_failure_ "$1" 358fi 359fi 360echo>&3"" 361} 362 363test_expect_success () { 364test"$#"=3&& { test_prereq=$1;shift; } || test_prereq= 365test"$#"=2|| 366 error "bug in the test script: not 2 or 3 parameters to test-expect-success" 367export test_prereq 368if! test_skip "$@" 369then 370 say >&3"expecting success:$2" 371if test_run_ "$2" 372then 373 test_ok_ "$1" 374else 375 test_failure_ "$@" 376fi 377fi 378echo>&3"" 379} 380 381# test_external runs external test scripts that provide continuous 382# test output about their progress, and succeeds/fails on 383# zero/non-zero exit code. It outputs the test output on stdout even 384# in non-verbose mode, and announces the external script with "# run 385# <n>: ..." before running it. When providing relative paths, keep in 386# mind that all scripts run in "trash directory". 387# Usage: test_external description command arguments... 388# Example: test_external 'Perl API' perl ../path/to/test.pl 389test_external () { 390test"$#"=4&& { test_prereq=$1;shift; } || test_prereq= 391test"$#"=3|| 392 error >&5"bug in the test script: not 3 or 4 parameters to test_external" 393 descr="$1" 394shift 395export test_prereq 396if! test_skip "$descr""$@" 397then 398# Announce the script to reduce confusion about the 399# test output that follows. 400 say_color """# run$test_count:$descr($*)" 401# Export TEST_DIRECTORY, TRASH_DIRECTORY and GIT_TEST_LONG 402# to be able to use them in script 403export TEST_DIRECTORY TRASH_DIRECTORY GIT_TEST_LONG 404# Run command; redirect its stderr to &4 as in 405# test_run_, but keep its stdout on our stdout even in 406# non-verbose mode. 407"$@"2>&4 408if["$?"=0] 409then 410iftest$test_external_has_tap-eq0;then 411 test_ok_ "$descr" 412else 413 say_color """# test_external test$descrwas ok" 414 test_success=$(($test_success + 1)) 415fi 416else 417iftest$test_external_has_tap-eq0;then 418 test_failure_ "$descr""$@" 419else 420 say_color error "# test_external test$descrfailed: $@" 421 test_failure=$(($test_failure + 1)) 422fi 423fi 424fi 425} 426 427# Like test_external, but in addition tests that the command generated 428# no output on stderr. 429test_external_without_stderr () { 430# The temporary file has no (and must have no) security 431# implications. 432 tmp=${TMPDIR:-/tmp} 433 stderr="$tmp/git-external-stderr.$$.tmp" 434 test_external "$@"4>"$stderr" 435[-f"$stderr"] || error "Internal error:$stderrdisappeared." 436 descr="no stderr:$1" 437shift 438 say >&3"# expecting no stderr from previous command" 439if[ !-s"$stderr"];then 440rm"$stderr" 441 442iftest$test_external_has_tap-eq0;then 443 test_ok_ "$descr" 444else 445 say_color """# test_external_without_stderr test$descrwas ok" 446 test_success=$(($test_success + 1)) 447fi 448else 449if["$verbose"= t ];then 450 output=`echo; echo "# Stderr is:"; cat "$stderr"` 451else 452 output= 453fi 454# rm first in case test_failure exits. 455rm"$stderr" 456iftest$test_external_has_tap-eq0;then 457 test_failure_ "$descr""$@""$output" 458else 459 say_color error "# test_external_without_stderr test$descrfailed: $@:$output" 460 test_failure=$(($test_failure + 1)) 461fi 462fi 463} 464 465# debugging-friendly alternatives to "test [-f|-d|-e]" 466# The commands test the existence or non-existence of $1. $2 can be 467# given to provide a more precise diagnosis. 468test_path_is_file () { 469if! [-f"$1"] 470then 471echo"File$1doesn't exist. $*" 472 false 473fi 474} 475 476test_path_is_dir () { 477if! [-d"$1"] 478then 479echo"Directory$1doesn't exist. $*" 480 false 481fi 482} 483 484test_path_is_missing () { 485if[-e"$1"] 486then 487echo"Path exists:" 488ls-ld"$1" 489if[$#-ge1];then 490echo"$*" 491fi 492 false 493fi 494} 495 496# test_line_count checks that a file has the number of lines it 497# ought to. For example: 498# 499# test_expect_success 'produce exactly one line of output' ' 500# do something >output && 501# test_line_count = 1 output 502# ' 503# 504# is like "test $(wc -l <output) = 1" except that it passes the 505# output through when the number of lines is wrong. 506 507test_line_count () { 508iftest$#!=3 509then 510 error "bug in the test script: not 3 parameters to test_line_count" 511elif!test$(wc -l <"$3")"$1""$2" 512then 513echo"test_line_count: line count for$3!$1$2" 514cat"$3" 515return1 516fi 517} 518 519# This is not among top-level (test_expect_success | test_expect_failure) 520# but is a prefix that can be used in the test script, like: 521# 522# test_expect_success 'complain and die' ' 523# do something && 524# do something else && 525# test_must_fail git checkout ../outerspace 526# ' 527# 528# Writing this as "! git checkout ../outerspace" is wrong, because 529# the failure could be due to a segv. We want a controlled failure. 530 531test_must_fail () { 532"$@" 533 exit_code=$? 534iftest$exit_code=0;then 535echo>&2"test_must_fail: command succeeded: $*" 536return1 537eliftest$exit_code-gt129-a$exit_code-le192;then 538echo>&2"test_must_fail: died by signal: $*" 539return1 540eliftest$exit_code=127;then 541echo>&2"test_must_fail: command not found: $*" 542return1 543eliftest$exit_code=126;then 544echo>&2"test_must_fail: valgrind error: $*" 545return1 546fi 547return0 548} 549 550# Similar to test_must_fail, but tolerates success, too. This is 551# meant to be used in contexts like: 552# 553# test_expect_success 'some command works without configuration' ' 554# test_might_fail git config --unset all.configuration && 555# do something 556# ' 557# 558# Writing "git config --unset all.configuration || :" would be wrong, 559# because we want to notice if it fails due to segv. 560 561test_might_fail () { 562"$@" 563 exit_code=$? 564iftest$exit_code-gt129-a$exit_code-le192;then 565echo>&2"test_might_fail: died by signal: $*" 566return1 567eliftest$exit_code=127;then 568echo>&2"test_might_fail: command not found: $*" 569return1 570fi 571return0 572} 573 574# Similar to test_must_fail and test_might_fail, but check that a 575# given command exited with a given exit code. Meant to be used as: 576# 577# test_expect_success 'Merge with d/f conflicts' ' 578# test_expect_code 1 git merge "merge msg" B master 579# ' 580 581test_expect_code () { 582 want_code=$1 583shift 584"$@" 585 exit_code=$? 586iftest$exit_code=$want_code 587then 588return0 589fi 590 591echo>&2"test_expect_code: command exited with$exit_code, we wanted$want_code$*" 592return1 593} 594 595# test_cmp is a helper function to compare actual and expected output. 596# You can use it like: 597# 598# test_expect_success 'foo works' ' 599# echo expected >expected && 600# foo >actual && 601# test_cmp expected actual 602# ' 603# 604# This could be written as either "cmp" or "diff -u", but: 605# - cmp's output is not nearly as easy to read as diff -u 606# - not all diff versions understand "-u" 607 608test_cmp() { 609$GIT_TEST_CMP"$@" 610} 611 612# Tests that its two parameters refer to the same revision 613test_cmp_rev () { 614 git rev-parse --verify"$1">expect.rev&& 615 git rev-parse --verify"$2">actual.rev&& 616 test_cmp expect.rev actual.rev 617} 618 619# Print a sequence of numbers or letters in increasing order. This is 620# similar to GNU seq(1), but the latter might not be available 621# everywhere (and does not do letters). It may be used like: 622# 623# for i in `test_seq 100`; do 624# for j in `test_seq 10 20`; do 625# for k in `test_seq a z`; do 626# echo $i-$j-$k 627# done 628# done 629# done 630 631test_seq () { 632case$#in 6331)set1"$@";; 6342) ;; 635*) error "bug in the test script: not 1 or 2 parameters to test_seq";; 636esac 637"$PERL_PATH"-le'print for$ARGV[0]..$ARGV[1]'--"$@" 638} 639 640# This function can be used to schedule some commands to be run 641# unconditionally at the end of the test to restore sanity: 642# 643# test_expect_success 'test core.capslock' ' 644# git config core.capslock true && 645# test_when_finished "git config --unset core.capslock" && 646# hello world 647# ' 648# 649# That would be roughly equivalent to 650# 651# test_expect_success 'test core.capslock' ' 652# git config core.capslock true && 653# hello world 654# git config --unset core.capslock 655# ' 656# 657# except that the greeting and config --unset must both succeed for 658# the test to pass. 659# 660# Note that under --immediate mode, no clean-up is done to help diagnose 661# what went wrong. 662 663test_when_finished () { 664 test_cleanup="{ $* 665 } && (exit\"\$eval_ret\"); eval_ret=\$?;$test_cleanup" 666} 667 668# Most tests can use the created repository, but some may need to create more. 669# Usage: test_create_repo <directory> 670test_create_repo () { 671test"$#"=1|| 672 error "bug in the test script: not 1 parameter to test-create-repo" 673 repo="$1" 674mkdir-p"$repo" 675( 676cd"$repo"|| error "Cannot setup test environment" 677"$GIT_EXEC_PATH/git-init""--template=$GIT_BUILD_DIR/templates/blt/">&3 2>&4|| 678 error "cannot run git init -- have you built things yet?" 679mv .git/hooks .git/hooks-disabled 680) ||exit 681} 682 683# This function helps on symlink challenged file systems when it is not 684# important that the file system entry is a symbolic link. 685# Use test_ln_s_add instead of "ln -s x y && git add y" to add a 686# symbolic link entry y to the index. 687 688test_ln_s_add () { 689if test_have_prereq SYMLINKS 690then 691ln-s"$1""$2"&& 692 git update-index --add"$2" 693else 694printf'%s'"$1">"$2"&& 695 ln_s_obj=$(git hash-object -w "$2")&& 696 git update-index --add --cacheinfo120000$ln_s_obj"$2" 697fi 698}