From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: ohler+emacs@fastmail.net, emacs-devel@gnu.org
Subject: Re: ert.el --- Emacs Lisp Regression Testing
Date: Sun, 06 Jan 2008 21:46:22 +0200 [thread overview]
Message-ID: <uodbyu48h.fsf@gnu.org> (raw)
In-Reply-To: <E1JBQa1-0001es-Ev@fencepost.gnu.org> (message from Richard Stallman on Sun, 06 Jan 2008 03:10:01 -0500)
> From: Richard Stallman <rms@gnu.org>
> CC: ohler+emacs@fastmail.net, emacs-devel@gnu.org
> Date: Sun, 06 Jan 2008 03:10:01 -0500
>
> For a general-purpose display testing, we need to add code to the
> display engine (both its high-level device-independent part, and
> lower-level display backend) that would expose to a Lisp application
> the glyphs that are produced by the display engine and the
> backend-dependent display commands sent to the display API
> (termcap/terminfo for text terminal, X for X Window system, etc.).
>
> That sounds like a big job, and most of it for no purpose other than
> testing.
I don't see why it would be a big job. Describing an iterator
structure and the glyph objects it produces is not hard, and neither
is the sequence of display API calls we issue to draw.
Anyway, if we ever want to have a regression testing suite for Emacs,
this job is hardly avoidable. Without a good test suite, any
significant changes to core machinery runs a high risk of introducing
new and exciting bugs.
next prev parent reply other threads:[~2008-01-06 19:46 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=uodbyu48h.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=ohler+emacs@fastmail.net \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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.