unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Christian Ohler <ohler+emacs@fastmail.net>
Cc: emacs-devel@gnu.org
Subject: Re: ert.el --- Emacs Lisp Regression Testing
Date: Mon, 31 Dec 2007 09:42:51 -0500	[thread overview]
Message-ID: <E1J9Lqt-0007Q8-GH@fencepost.gnu.org> (raw)
In-Reply-To: <47782302.5000201@fastmail.net> (message from Christian Ohler on Mon, 31 Dec 2007 00:00:18 +0100)

ert.el looks very useful.  Would you like to contribute it to Emacs?

One of the things that has held us back from setting up a test suite
in the past is that only a minority of Emacs bugs concern Lisp progrmming.
Most Emacs bugs involve keyboard commands and/or redisplay.

It occurs to me that M-x term could be used to test for redisplay.
The idea is that you run a sub-Emacs, send it commands, and check what
it displayed (because what it displayed is now in a buffer).

It would be terribly slow to do this starting a new sub-Emacs for each
test.  So the test framework ought to be designed to do many such tests
with the same sub-Emacs, clearing out whatever is necessary each time.

I think that an extension to ert.el, for sub-Emacs testing, might make
it easy to define those tests, much as ert.el makes it easy to define
tests of Lisp execution.

Interested?

  parent reply	other threads:[~2007-12-31 14:42 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 [this message]
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

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=E1J9Lqt-0007Q8-GH@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=ohler+emacs@fastmail.net \
    /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).