From: Felipe Contreras <felipe.contreras@xxxxxxxxx>
In the tests involving @{-1} and @{u} as the final component, what we
really want to check is if it's pointing to the right ref. We
currently check the tip commit of the ref, but we can clarify this by
separating out checking for commits versus checking for refs at
check().
[rr: commit message, fix arguments in check()]
Signed-off-by: Ramkumar Ramachandra <artagnon@xxxxxxxxx>
---
t/t1508-at-combinations.sh | 27 ++++++++++++++++-----------
1 file changed, 16 insertions(+), 11 deletions(-)
diff --git a/t/t1508-at-combinations.sh b/t/t1508-at-combinations.sh
index 46e3f16..cacb2d0 100755
--- a/t/t1508-at-combinations.sh
+++ b/t/t1508-at-combinations.sh
@@ -4,9 +4,14 @@ test_description='test various @{X} syntax combinations together'
. ./test-lib.sh
check() {
-test_expect_${3:-success} "$1 = $2" "
- echo '$2' >expect &&
- git log -1 --format=%s '$1' >actual &&
+test_expect_${4:-success} "$1 = ${3:-$2}" "
+ if [ '$2' == 'commit' ]; then
+ echo '$3' >expect &&
+ git log -1 --format=%s '$1' >actual
+ else
+ echo '${3:-$2}' >expect &&
+ git rev-parse --symbolic-full-name '$1' >actual
+ fi &&
test_cmp expect actual
"
}
@@ -35,14 +40,14 @@ test_expect_success 'setup' '
git branch -u upstream-branch new-branch
'
-check HEAD new-two
-check "@{1}" new-one
-check "@{-1}" old-two
-check "@{-1}@{1}" old-one
-check "@{u}" upstream-two
-check "@{u}@{1}" upstream-one
-check "@{-1}@{u}" master-two
-check "@{-1}@{u}@{1}" master-one
+check HEAD refs/heads/new-branch
+check "@{1}" commit new-one
+check "@{-1}" refs/heads/old-branch
+check "@{-1}@{1}" commit old-one
+check "@{u}" refs/heads/upstream-branch
+check "@{u}@{1}" commit upstream-one
+check "@{-1}@{u}" refs/heads/master
+check "@{-1}@{u}@{1}" commit master-one
nonsense "@{u}@{-1}"
nonsense "@{1}@{u}"
--
1.8.3.rc0.40.g09a0447
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html