git-commit-vandalism/t/chainlint/case.expect

(
	case "$x" in
	x) foo ;;
	*) bar ;;
	esac &&
	foobar
>) &&
(
	case "$x" in
	x) foo ;;
	*) bar ;;
?!AMP?!	esac
	foobar
>) &&
(
	case "$x" in 1) true;; esac &&
?!AMP?!	case "$y" in 2) false;; esac
	foobar
>)
t/chainlint: add chainlint "loop" and "conditional" test cases The --chain-lint option uses heuristics and knowledge of shell syntax to detect broken &&-chains in subshells by pure textual inspection. The heuristics handle a range of stylistic variations in existing tests (evolved over the years), however, they are still best-guesses. As such, it is possible for future changes to accidentally break assumptions upon which the heuristics are based. Protect against this possibility by adding tests which check the linter itself for correctness. In addition to protecting against regressions, these tests help document (for humans) expected behavior, which is important since the linter's implementation language ('sed') does not necessarily lend itself to easy comprehension. Signed-off-by: Eric Sunshine <sunshine@sunshineco.com> Signed-off-by: Junio C Hamano <gitster@pobox.com> 2018-07-11 08:46:39 +02:00			`(`
			`case "$x" in`
			`x) foo ;;`
			`*) bar ;;`
			`esac &&`
			`foobar`
			`>) &&`
			`(`
			`case "$x" in`
			`x) foo ;;`
			`*) bar ;;`
			`?!AMP?! esac`
			`foobar`
			`>) &&`
			`(`
			`case "$x" in 1) true;; esac &&`
			`?!AMP?! case "$y" in 2) false;; esac`
			`foobar`
			`>)`