All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mathias Lafeldt <mathias.lafeldt@gmail.com>
To: git@vger.kernel.org
Subject: [ANNOUNCE] Sharness - Test library derived from Git
Date: Tue, 17 Jul 2012 10:06:45 +0200	[thread overview]
Message-ID: <CAMFa-2hS-5CHQj79KMGwY7_qv6nGiK+9cKeDdihMVmSoxfsesQ@mail.gmail.com> (raw)

Hi,

I've been wanting to announce Sharness [1] on this list for quite some
time now, but never managed to do so. With the release of version
0.2.4, I think it's about time to change that.

Sharness is a shell-based test harness library. It was derived from
the Git project and is basically a generalized and stripped-down
version of t/test-lib.sh (I basically removed all things specific to
Git). So when you know how to write tests for Git, it should be very
familiar.

I've been using Sharness to test my command-line applications [2] for
over a year now. It's especially useful when you're doing continuous
integration with a service like Travis CI [3].

Development of Sharness takes place at GitHub [4]. If you're
interested, there might be some things I could contribute back to Git,
e.g. the API documentation [5] I wrote in TomDoc format.

Looking forward to your feedback.

[1] http://mlafeldt.github.com/sharness
[2] https://github.com/mlafeldt/sharness#projects-using-sharness
[3] http://travis-ci.org/
[4] https://github.com/mlafeldt/sharness
[5] https://github.com/mlafeldt/sharness/blob/master/API.md

-Mathias

             reply	other threads:[~2012-07-17  8:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-17  8:06 Mathias Lafeldt [this message]
2012-07-17 18:31 ` [ANNOUNCE] Sharness - Test library derived from Git Ævar Arnfjörð Bjarmason
2012-07-20 10:18   ` Mathias Lafeldt
2012-07-20 11:45     ` Matthieu Moy
2012-07-20 21:11       ` dag

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=CAMFa-2hS-5CHQj79KMGwY7_qv6nGiK+9cKeDdihMVmSoxfsesQ@mail.gmail.com \
    --to=mathias.lafeldt@gmail.com \
    --cc=git@vger.kernel.org \
    /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.