From: "René Scharfe" <l.s.r@web.de>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: Git Mailing List <git@vger.kernel.org>, Jeff King <peff@peff.net>,
Junio C Hamano <gitster@pobox.com>,
Christian Couder <chriscool@tuxfamily.org>
Subject: Re: [PATCH 1/2] sha1-array: add test-sha1-array and basic tests
Date: Wed, 01 Oct 2014 16:21:22 +0200 [thread overview]
Message-ID: <542C0DE2.6060502@web.de> (raw)
In-Reply-To: <CAPig+cQxXccnQCwr7oVfccAQn3sTUpv=b=qHEX1H7abng--=0A@mail.gmail.com>
Am 01.10.2014 um 16:11 schrieb Eric Sunshine:
> On Wed, Oct 1, 2014 at 5:40 AM, René Scharfe <l.s.r@web.de> wrote:
>> Signed-off-by: Rene Scharfe <l.s.r@web.de>
>> ---
>> diff --git a/t/t0064-sha1-array.sh b/t/t0064-sha1-array.sh
>> new file mode 100755
>> index 0000000..bd68789
>> --- /dev/null
>> +++ b/t/t0064-sha1-array.sh
>> @@ -0,0 +1,64 @@
>> +#!/bin/sh
>> +
>> +test_description='basic tests for the SHA1 array implementation'
>> +. ./test-lib.sh
>> +
>> +echo20() {
>> + prefix="$1"
>> + shift
>> + while test $# -gt 0
>> + do
>> + echo "$prefix$1$1$1$1$1$1$1$1$1$1$1$1$1$1$1$1$1$1$1$1"
>
> Each caller of echo20() manually includes a space at the end of
> $prefix. Would it make sense to instead have echo20() do this on
> behalf of the caller?
>
> echo "$prefix $1$1$1$1$1$1$1$1$1$1$1$1$1$1$1$1$1$1$1$1"
That wouldn't work if the prefix is the empty string; we don't want a
space in that case (see the next echo20 call below).
But ${prefix:+$prefix } would do the trick. Thanks for the idea. :)
>
>> + shift
>> + done
>> +}
>> +
>> +test_expect_success 'ordered enumeration' '
>> + echo20 "" 44 55 88 aa >expect &&
>> + {
>> + echo20 "append " 88 44 aa 55 &&
>
> Which would slightly reduce the burden on the caller and make it read
> (very slightly) nicer:
>
> echo20 append 88 44 aa 55 &&
>
>> + echo for_each_unique
>> + } | test-sha1-array >actual &&
>> + test_cmp expect actual
>> +'
>> +
>> +test_expect_success 'ordered enumeration with duplicate suppression' '
>> + echo20 "" 44 55 88 aa >expect &&
>> + {
>> + echo20 "append " 88 44 aa 55 &&
>> + echo20 "append " 88 44 aa 55 &&
>> + echo for_each_unique
>> + } | test-sha1-array >actual &&
>> + test_cmp expect actual
>> +'
>> +
>> +test_expect_success 'lookup' '
>> + {
>> + echo20 "append " 88 44 aa 55 &&
>> + echo20 "lookup " 55
>> + } | test-sha1-array >actual &&
>> + n=$(cat actual) &&
>> + test "$n" -eq 1
>> +'
>> +
>> +test_expect_success 'lookup non-existing entry' '
>> + {
>> + echo20 "append " 88 44 aa 55 &&
>> + echo20 "lookup " 33
>> + } | test-sha1-array >actual &&
>> + n=$(cat actual) &&
>> + test "$n" -lt 0
>> +'
>> +
>> +test_expect_success 'lookup with duplicates' '
>> + {
>> + echo20 "append " 88 44 aa 55 &&
>> + echo20 "append " 88 44 aa 55 &&
>> + echo20 "lookup " 55
>> + } | test-sha1-array >actual &&
>> + n=$(cat actual) &&
>> + test "$n" -ge 2 &&
>> + test "$n" -le 3
>> +'
>> +
>> +test_done
next prev parent reply other threads:[~2014-10-01 14:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-01 9:40 [PATCH 1/2] sha1-array: add test-sha1-array and basic tests René Scharfe
2014-10-01 9:43 ` [PATCH 2/2] sha1-lookup: fix handling of duplicates in sha1_pos() René Scharfe
2014-10-01 10:50 ` Jeff King
2014-10-01 11:10 ` René Scharfe
2014-10-01 12:33 ` Jeff King
2014-10-01 14:12 ` Eric Sunshine
2014-10-01 14:11 ` [PATCH 1/2] sha1-array: add test-sha1-array and basic tests Eric Sunshine
2014-10-01 14:21 ` René Scharfe [this message]
2014-10-01 14:23 ` Jeff King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=542C0DE2.6060502@web.de \
--to=l.s.r@web.de \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=sunshine@sunshineco.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.