From: Glenn Morris <rgm@gnu.org>
To: Matt McClure <matthewlmcclure@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: What tools and references do you use for Emacs Lisp unit testing?
Date: Tue, 03 Apr 2012 18:10:59 -0400 [thread overview]
Message-ID: <n2398k4gb0.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <CAJELnLGCLakbcAA81Gro0b4rdFyw6DZOLgh0pTG67oPgkpGstQ@mail.gmail.com> (Matt McClure's message of "Tue, 3 Apr 2012 00:11:27 -0400")
Matt McClure wrote:
> I've written a bit of Emacs Lisp, and I've written unit tests in other
> languages. From the list of tools on http://emacswiki.org/emacs/UnitTesting,
> ert.el and el-expectations.el look most promising to me. What tools are
> others using for unit testing and TDD in Emacs Lisp? What are good examples
> of packages using each?
Well, ERT is included in Emacs (from 24.1 onwards), together with a nice
manual, and is used for the (so far, somewhat sparse) tests in the
test/automated directory in the Emacs repository.
next prev parent reply other threads:[~2012-04-03 22:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-03 4:11 What tools and references do you use for Emacs Lisp unit testing? Matt McClure
2012-04-03 22:10 ` Glenn Morris [this message]
2012-04-06 5:04 ` Jeremiah Dodds
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: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=n2398k4gb0.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=help-gnu-emacs@gnu.org \
--cc=matthewlmcclure@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 read-only IMAP folder(s) and NNTP newsgroup(s).