git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Christian Couder <christian.couder@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Jeff King" <peff@peff.net>,
	"SZEDER Gábor" <szeder.dev@gmail.com>, git <git@vger.kernel.org>,
	"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
	"Jonathan Tan" <jonathantanmy@google.com>,
	"Brandon Williams" <bmwill@google.com>,
	"Christian Couder" <chriscool@tuxfamily.org>
Subject: Re: [PATCH 2/3] t: add t0016-oidmap.sh
Date: Fri, 14 Jun 2019 12:36:02 +0200	[thread overview]
Message-ID: <CAP8UFD3Q2rQwq82LNSXuLSEUMHABVJVgy8UJ7Fvgxug1rZGMFQ@mail.gmail.com> (raw)
In-Reply-To: <xmqqh88tunvt.fsf@gitster-ct.c.googlers.com>

On Fri, Jun 14, 2019 at 12:22 AM Junio C Hamano <gitster@pobox.com> wrote:
>
> Jeff King <peff@peff.net> writes:
>
> >> > I know there are testing philosophies that go to this level of
> >> > white-box testing, but I don't think we usually do in Git. A unit
> >> > test of oidmap's externally visible behavior seems like the right
> >> > level to me.
> >>
> >> That's a good point...  but then why does 't0011-hashmap.sh' do it in
> >> the first place?  As far as I understood this t0016 mainly follows
> >> suit of t0011.
> >
> > I'd make the same argument against t0011. :)
>
> Yeah, I tend to agree.  It is not a good excuse that somebody else
> alerady has made a mistake.

Ok, I will remove the "hash" test in t0016 and the corresponding code
in test-oidmap.c.

> > I think there it at least made a little more sense because we truly are
> > hashing ourselves, rather than just copying out some sha1 bytes. But I
> > think I'd still argue that if I updated strhash() to use a different
> > hash, I should not have to be updating t0011 to change out the hashes.
>
> True, too.

I will also send an additional patch to remove similar code in t00161
and test-hashmap.c.

  reply	other threads:[~2019-06-14 10:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-09  4:49 [PATCH 0/3] Test oidmap Christian Couder
2019-06-09  4:49 ` [PATCH 1/3] t/helper: add test-oidmap.c Christian Couder
2019-06-09  4:49 ` [PATCH 2/3] t: add t0016-oidmap.sh Christian Couder
2019-06-09  9:22   ` SZEDER Gábor
2019-06-09 20:24     ` Christian Couder
2019-06-09 21:21       ` SZEDER Gábor
2019-06-09 21:51         ` Christian Couder
2019-06-10 16:46     ` Junio C Hamano
2019-06-13 17:19     ` Jeff King
2019-06-13 17:52       ` SZEDER Gábor
2019-06-13 19:02         ` Jeff King
2019-06-13 22:22           ` Junio C Hamano
2019-06-14 10:36             ` Christian Couder [this message]
2019-06-09  4:49 ` [PATCH 3/3] oidmap: use sha1hash() instead of static hash() function Christian Couder

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAP8UFD3Q2rQwq82LNSXuLSEUMHABVJVgy8UJ7Fvgxug1rZGMFQ@mail.gmail.com \
    --to=christian.couder@gmail.com \
    --cc=avarab@gmail.com \
    --cc=bmwill@google.com \
    --cc=chriscool@tuxfamily.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jonathantanmy@google.com \
    --cc=peff@peff.net \
    --cc=szeder.dev@gmail.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).