From: Christian Ohler <ohler+emacs@fastmail.net>
To: Phil Hagelberg <phil@evri.com>
Cc: emacs-devel@gnu.org
Subject: Re: ert.el --- Emacs Lisp Regression Testing
Date: Sat, 05 Jan 2008 12:32:44 +0100 [thread overview]
Message-ID: <477F6ADC.9060502@fastmail.net> (raw)
In-Reply-To: <85ir2arbix.fsf@evri.com>
Phil Hagelberg, 2008-01-03:
> I'm the author of elunit. I'm obviously very interested in unit testing
> in Emacs Lisp (preferably test-driven development, but any tests are
> good.) elunit has mostly been driven by my own needs, so it's no
> surprise that it doesn't seem like a great fit for everyone, but I would
> love to see unit testing get more traction in the Emacs community,
> whether it's through elunit or ERT.
I'm familiar with (an earlier version of) elunit; I've used it for
writing a test suite for xmtn (a DVC backend for the distributed version
control system monotone). It served its purpose, but I wanted something
that offers an even better workflow for test-driven development. None
of the existing tools did that.
> ERT looks several orders of magnitude more complicated than elunit, but
> obviously it has a lot more functionality.
There are some parts in ERT that can be simplified, but the parts that
are really tricky (`ert-run-test-debugger' and friends and `should') are
inherently tricky. Other tools take simpler approaches but have less
functionality and are less general.
> I've beaten my head against the problem of testing with a fresh
> instance, and it's always been rather awkward.
Hmm, what do you mean here? What were your goals, what was your
approach, and why were you unhappy with the results?
I skimmed your page on behave.el ( http://dev.technomancy.us/Behave.el
). What are its main features? Adding tags and docstrings to ERT would
not be difficult. I think ERT's `should' is already more powerful than
behave.el's `expect'.
I would like to look at your code, but the command from
http://dev.technomancy.us/DotFiles ,
git clone http://git.caboo.se/technomancy.git
says
Cannot get remote repository information.
Perhaps git-update-server-info needs to be run there?
Christian.
prev parent reply other threads:[~2008-01-05 11:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-30 23:00 ert.el --- Emacs Lisp Regression Testing Christian Ohler
2007-12-30 23:28 ` Lennart Borgman (gmail)
2008-01-05 11:32 ` Christian Ohler
2007-12-31 14:42 ` Richard Stallman
2008-01-05 11:32 ` Christian Ohler
2008-01-05 13:06 ` Eli Zaretskii
2008-01-06 8:10 ` Richard Stallman
2008-01-06 19:46 ` Eli Zaretskii
2008-01-07 11:31 ` Richard Stallman
2008-01-07 13:00 ` Mike Mattie
2008-01-03 18:48 ` Phil Hagelberg
2008-01-05 11:32 ` Christian Ohler [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
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=477F6ADC.9060502@fastmail.net \
--to=ohler+emacs@fastmail.net \
--cc=emacs-devel@gnu.org \
--cc=phil@evri.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).