From: Lennart Borgman <lennart.borgman@gmail.com>
To: Christian Ohler <ohler+emacs@fastmail.net>
Cc: Nikolaj Schumacher <me@nschum.de>,
web@shellarchive.co.uk, Masatake YAMATO <yamato@redhat.com>,
joakim@verona.se, emacs-devel@gnu.org,
rubikitch <rubikitch@ruby-lang.org>,
Stefan Monnier <monnier@iro.umontreal.ca>,
Phil Hagelberg <phil@hagelb.org>
Subject: Re: unit test framework
Date: Sat, 12 Jun 2010 15:48:35 +0200 [thread overview]
Message-ID: <AANLkTimASZ7ZagVbJl39ANpXRAafyO06dyIdrU2LO8V9@mail.gmail.com> (raw)
In-Reply-To: <4C1323F5.80301@fastmail.net>
On Sat, Jun 12, 2010 at 8:06 AM, Christian Ohler
<ohler+emacs@fastmail.net> wrote:
>
> It does not yet include utilities for testing Emacs state such as window
> layouts and buffer contents with text properties, or user input, but such
> utilities are orthogonal to the basic test execution framework and can be
> added incrementally. I think Lennart has some of this already in his fork.
My additions are for running commands (i.e. running the necessary
hooks in hopefully correct order) and for testing of fontification.
There is also a little bit for adding a test input file for a test.
And a bit for keeping track of the test name.
But I suggest you review my code and tweak it to your liking. Please
contact me off list.
> I have some spare time now and can offer to work on integrating ert into
> Emacs; any suggestions where to start? Where does a file like ert.el
> belong? Where should the corresponding tests go?
There is already a sub-directory for tests, "emacs/test". To my
surprise the elisp files for test also is there. I suggest these
should be somewhere like "emacs/lisp/test" instead and that
"emacs/test" will be for data files etc instead.
An objection to this might be that the tests can't be run without the
data. Yes, but the code in the elisp files can serve as examples for
those writing tests.
next prev parent reply other threads:[~2010-06-12 13:48 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-18 7:39 unit test framework Masatake YAMATO
2010-03-18 9:31 ` Lennart Borgman
2010-03-18 10:07 ` Leo
2010-03-18 10:23 ` Lennart Borgman
2010-03-18 11:25 ` Masatake YAMATO
2010-03-18 14:22 ` Stefan Monnier
2010-03-18 14:56 ` Lennart Borgman
2010-03-19 0:16 ` rubikitch
2010-03-19 19:00 ` Phil Hagelberg
2010-03-20 11:01 ` Nikolaj Schumacher
2010-03-23 9:02 ` joakim
2010-03-23 13:15 ` Lennart Borgman
2010-03-24 3:03 ` Masatake YAMATO
2010-03-23 14:22 ` Stefan Monnier
2010-04-13 10:32 ` joakim
2010-06-12 6:06 ` Christian Ohler
2010-06-12 13:48 ` Lennart Borgman [this message]
2010-06-14 11:24 ` Masatake YAMATO
2010-07-23 21:58 ` Stefan Monnier
2010-03-23 10:15 ` Philip Jackson
2010-06-27 18:50 ` Philip Jackson
2010-07-09 13:43 ` Christian Ohler
2010-07-09 23:01 ` Glenn Morris
2010-07-10 1:12 ` 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=AANLkTimASZ7ZagVbJl39ANpXRAafyO06dyIdrU2LO8V9@mail.gmail.com \
--to=lennart.borgman@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=joakim@verona.se \
--cc=me@nschum.de \
--cc=monnier@iro.umontreal.ca \
--cc=ohler+emacs@fastmail.net \
--cc=phil@hagelb.org \
--cc=rubikitch@ruby-lang.org \
--cc=web@shellarchive.co.uk \
--cc=yamato@redhat.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 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.