summaryrefslogtreecommitdiff
path: root/t/chainlint/broken-chain.expect
diff options
context:
space:
mode:
authorEric Sunshine <sunshine@sunshineco.com>2018-07-11 06:46:35 (GMT)
committerJunio C Hamano <gitster@pobox.com>2018-07-17 16:15:14 (GMT)
commit5238710eb404cc81de511743811f92759cb7ca7b (patch)
tree23b170c8029625a1f149db0b2d9b28dd47fe3385 /t/chainlint/broken-chain.expect
parent803394459d40f8d07cef11d49900ba6f72887869 (diff)
downloadgit-5238710eb404cc81de511743811f92759cb7ca7b.zip
git-5238710eb404cc81de511743811f92759cb7ca7b.tar.gz
git-5238710eb404cc81de511743811f92759cb7ca7b.tar.bz2
t/chainlint: add chainlint "basic" 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>
Diffstat (limited to 't/chainlint/broken-chain.expect')
-rw-r--r--t/chainlint/broken-chain.expect6
1 files changed, 6 insertions, 0 deletions
diff --git a/t/chainlint/broken-chain.expect b/t/chainlint/broken-chain.expect
new file mode 100644
index 0000000..55b0f42
--- /dev/null
+++ b/t/chainlint/broken-chain.expect
@@ -0,0 +1,6 @@
+(
+ foo &&
+?!AMP?! bar
+ baz &&
+ wop
+>)