From: Lea Wiemann <lewiemann@gmail.com>
To: Petr Baudis <pasky@suse.cz>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: perl/Git.pm: Writing a test suite
Date: Fri, 30 May 2008 15:44:11 +0200 [thread overview]
Message-ID: <484004AB.40008@gmail.com> (raw)
In-Reply-To: <20080530100306.GF18781@machine.or.cz>
Petr Baudis wrote:
> Lea Wiemann wrote:
>> it would seem sensible to me to create mock output for the external calls
>
> I think this is bad idea; you should test not just Git.pm
> functionality, but equally importantly also its integration with
> (current version of) Git.
Good point. So I'll work on test repositories with real calls to Git
where possible.
> There are two possible ways, either using the Git test suite
> infrastructure, or the Perl test suite infrastructure.
I'd definitely want to use Perl's testing infrastructure, but probably
it's sensible to use both Git's and Perl's infrastructure (e.g. call the
Git.pm perl tests from the Git test suite shell scripts, and maybe have
setup code in the shell scripts). Here are two questions:
1. Is it OK for the Git.pm tests to be called from the Git test scripts
but generate different-looking output (since the tests are run in Perl)?
2. I might need external test helpers from CPAN at some point. Is that
a bad idea because of dependencies, or are we OK with having additional
dependencies for running the test suite if necessary?
-- Lea
next prev parent reply other threads:[~2008-05-30 13:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-30 7:43 perl/Git.pm: Writing a test suite Lea Wiemann
2008-05-30 8:03 ` Rafael Garcia-Suarez
2008-05-30 10:03 ` Petr Baudis
2008-05-30 13:44 ` Lea Wiemann [this message]
2008-05-30 20:28 ` Junio C Hamano
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=484004AB.40008@gmail.com \
--to=lewiemann@gmail.com \
--cc=git@vger.kernel.org \
--cc=pasky@suse.cz \
/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).