unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: dhruva <dhruvakm@gmail.com>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Need for a Emacs regression test suite
Date: Tue, 11 Sep 2007 05:12:52 +0900	[thread overview]
Message-ID: <87tzq25lff.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <e3f230850709082119s92e13abi65f674b3b0c9b171@mail.gmail.com>

dhruva writes:

 > I request Stephen to provide me some links that can help me understand
 > and get it up and running for Emacs. Hope it is hackable with average
 > Elisp knowledge.

Basically, just get a copy of the XEmacs sources and the test suite is
self-contained, in the tests/automated directory.

The testing framework itself is in the file test-harness.el.  The
tests, which are more or less organized according to subsystem, are in
files named MODULE-tests.el.  (These files are never byte-compiled to
.elcs; instead, the tests are run both uncompiled and compiled, with
compilation being done on the fly.)

The only link I can give off hand is mailto:stephen@xemacs.org. :-)  I
will certainly contribute to any work on the test suite to make it
work with Emacs, because that is an excellent way to identify, and
with luck in many cases eliminate, gratuitous differences between the
two.

There may be some information in the Internals manual, but in fact
writing most tests is "mere scripting".  We have some macros such as
Assert to actually run a test and check for correct values, CheckError
to run a test of invalid code and check that it raises the correct
error condition, and so on.  If you can write recipe to identify a
bug, then you just wrap it in one of those macros.  Eg, to test
addition you could do

  (Assert (= (+ 1 1) 2))

and you're done.

  parent reply	other threads:[~2007-09-10 20:12 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-08 17:51 Need for a Emacs regression test suite dhruva
2007-09-08 18:19 ` Lennart Borgman (gmail)
2007-09-08 20:22 ` Stephen J. Turnbull
     [not found] ` <E1IUCJD-0000Zk-BP@fencepost.gnu.org>
     [not found]   ` <e3f230850709082119s92e13abi65f674b3b0c9b171@mail.gmail.com>
2007-09-09  8:05     ` David Kastrup
2007-09-09  9:45       ` Lennart Borgman (gmail)
2007-09-09 10:13         ` David Kastrup
2007-09-09 20:06     ` Richard Stallman
2007-09-10 19:08       ` Stephen J. Turnbull
2007-09-10 19:12         ` Davis Herring
2007-09-11  5:00         ` Mathias Dahl
2007-09-11  6:08           ` Stephen J. Turnbull
2007-09-11 20:30         ` Richard Stallman
2007-09-12  4:44           ` Stephen J. Turnbull
2007-09-13 16:29             ` Richard Stallman
2007-09-10 20:12     ` Stephen J. Turnbull [this message]
2007-09-11  3:50       ` dhruva
2007-09-11 14:43         ` Stephen J. Turnbull
2007-09-11 19:33         ` Eli Zaretskii

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=87tzq25lff.fsf@uwakimon.sk.tsukuba.ac.jp \
    --to=stephen@xemacs.org \
    --cc=dhruvakm@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=rms@gnu.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.
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).