From: "Rafael Garcia-Suarez" <rgarciasuarez@gmail.com>
To: "Lea Wiemann" <lewiemann@gmail.com>
Cc: "Git Mailing List" <git@vger.kernel.org>
Subject: Re: perl/Git.pm: Writing a test suite
Date: Fri, 30 May 2008 10:03:54 +0200 [thread overview]
Message-ID: <b77c1dce0805300103ke5f0259m336ace5f6f7e2e30@mail.gmail.com> (raw)
In-Reply-To: <483FB034.3050507@gmail.com>
2008/5/30 Lea Wiemann <lewiemann@gmail.com>:
> Git.pm doesn't currently have a test suite, and I think it should get one.
>
> Since Git.pm makes calls to the git binary, it would seem sensible to me to
> create mock output for the external calls, like Grit (a Ruby API) does it,
> here: http://github.com/mojombo/grit/tree/master/test/fixtures (Having a
> complete test repository to test against like Ruby/Git (another API) at
> http://repo.or.cz/w/rubygit.git?a=tree;f=tests/files;hb=HEAD is probably too
> brittle and makes it hard to test edge cases.)
>
> I haven't done testing in perl before, so if someone wants to exchange ideas
> and/or help me get this set up, please post here or message me on IRC
> (lea_w/lea_1 on #git at Freenode).
Testing is big in the perl world. I suggest to start with reading :
http://www.perlfoundation.org/perl5/index.cgi?testing
I'm not overloaded with tuits at the moment, but I'll try to review a
bit your testing patches when you post them here.
next prev parent reply other threads:[~2008-05-30 8:05 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 [this message]
2008-05-30 10:03 ` Petr Baudis
2008-05-30 13:44 ` Lea Wiemann
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=b77c1dce0805300103ke5f0259m336ace5f6f7e2e30@mail.gmail.com \
--to=rgarciasuarez@gmail.com \
--cc=git@vger.kernel.org \
--cc=lewiemann@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.
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).