From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org, "Lukas Sandström" <luksan@gmail.com>,
"Jay Soffian" <jaysoffian@gmail.com>,
"John Szakmeister" <john@szakmeister.net>,
"Erik Faye-Lund" <kusmabite@gmail.com>,
"Ted Zlatanov" <tzz@lifelogs.com>
Subject: Re: credential helper tests
Date: Fri, 23 Sep 2011 15:26:16 -0700 [thread overview]
Message-ID: <7v7h4yuc8n.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20110923221513.GA3087@sigill.intra.peff.net> (Jeff King's message of "Fri, 23 Sep 2011 18:15:13 -0400")
Jeff King <peff@peff.net> writes:
> Since we've had a few credential helpers posted to the list recently, I
> really want to try them all out. This can be a little bit tricky for
> automated testing, though, for two reasons:
>
> - they run on lots of platforms with lots of dependencies
>
> - they interact with parts of the systems that are opaque to git. So
> we can't make a test that reliably simulates "and then the user
> types 'foo' into a dialog box" across all platforms.
>
> Instead, I came up with a separate test script that is intended to be
> run interactively with the user. It runs the helpers through a battery
> of tests, and tells the user what to expect and what to input to any
> dialogs or prompts.
>
> I've run it already on the helpers I've written. I plan on running it
> with the helpers that have been posted, as well. But I also wanted to
> make it public so that authors could use it as a development aid.
>
> It's not integrated with git's tests at all. In theory it could be part
> of t/, but disabled unless the user asks for it. However, I'm not sure
> that makes much sense. It's intended to test helpers that aren't
> necessarily even shipped with git, and wouldn't necessarily even need
> git to run.
Perhaps throw it in somewhere under contrib/ hierarchy?
prev parent reply other threads:[~2011-09-23 22:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-23 22:15 credential helper tests Jeff King
2011-09-23 22:26 ` Junio C Hamano [this message]
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=7v7h4yuc8n.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jaysoffian@gmail.com \
--cc=john@szakmeister.net \
--cc=kusmabite@gmail.com \
--cc=luksan@gmail.com \
--cc=peff@peff.net \
--cc=tzz@lifelogs.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 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 NNTP newsgroup(s).