From: joakim@verona.se
To: emacs-devel <emacs-devel@gnu.org>
Cc: lennart.borgman@gmail.com
Subject: Re: when emacs 22.1 release will ready?
Date: Mon, 30 Apr 2007 12:15:46 +0200 [thread overview]
Message-ID: <m3tzuycgml.fsf@kurono.home> (raw)
In-Reply-To: <4635B7F9.8090909@gmail.com> (Lennart Borgman's message of "Mon\, 30 Apr 2007 11\:33\:45 +0200")
"Lennart Borgman (gmail)" <lennart.borgman@gmail.com> writes:
>> With a similar release procedure for Emacs, Emacs 22.1 had been
>> released in 2004, and 23.4 would be ready for release next month.
>
> What do they do to keep control over the quality? I guess they are
> using a lot of unit testing for the kernel, or?
>
> Is that something that could be done for Emacs? I would propose that
> this should be done, in a proper manner. The way I would like to see
> it done is to add unit tests when relevant. There are a few points to
> watch out for:
>
> - Any change.
> - Any bug reports.
> - Any code that is hard to understand.
>
> A problem is of course that Emacs is screen oriented and that it is
> much harder to have an automatic testing framework for that. I do not
> know how people do that now, but semi-automatic result testing should
> be possible in cases for fully automatic testing is not possible.
I wrote some simple unit-test for CEDET
(http://www.emacswiki.org/cgi-bin/wiki/CollectionOfEmacsDevelopmentEnvironmentTools)
Having done so, I think emacs is fairly well suited for unit-tesing.
This is because, unlike many gui applications, things dont move around
very randomly in an emacs buffer. You can set-up a buffer to, for
instance, test font-locking. At a given character position you will
expect to find a certain property, if it works.
You have also the possibility to create macros, which re-create a
certain test environment, fairly conveniently with inbuilt emacs
facilities.
The problem is of course to get developers interested in creating
unit-test.
Another useful method is getting bug-reporters to supply unit tests
for their bugs.
If some unit-testing frameworks, like
http://www.emacswiki.org/cgi-bin/wiki/UnitTesting, where included in
emacs, maybe the bug-reporting template in emacs could suggest writing
a unit test for the bug when reporting it.
> Of course, this is work and it takes time. But if the impression that
> changes create regression is valid then I think something like the
> above is a possible way to get out of it and get shorter release
> cycles.
--
Joakim Verona
next prev parent reply other threads:[~2007-04-30 10:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-29 20:37 when emacs 22.1 release will ready? Alex Ott
2007-04-30 9:21 ` Kim F. Storm
2007-04-30 9:33 ` Lennart Borgman (gmail)
2007-04-30 9:38 ` Jason Rumney
2007-04-30 9:53 ` Lennart Borgman (gmail)
2007-04-30 19:10 ` Eli Zaretskii
2007-04-30 21:30 ` Lennart Borgman (gmail)
2007-04-30 23:29 ` Juanma Barranquero
2007-04-30 9:56 ` Thomas Hühn
2007-04-30 10:18 ` Lennart Borgman (gmail)
2007-04-30 10:15 ` joakim [this message]
2007-04-30 10:25 ` Lennart Borgman (gmail)
2007-04-30 22:10 ` Richard Stallman
2007-04-30 15:18 ` unit testing [was Re: when emacs 22.1 release will ready?] Stephen J. Turnbull
2007-04-30 10:09 ` when emacs 22.1 release will ready? Leo
2007-04-30 10:23 ` Lennart Borgman (gmail)
2007-04-30 10:37 ` Leo
2007-04-30 11:29 ` Thien-Thi Nguyen
2007-04-30 15:20 ` Chong Yidong
2007-04-30 23:26 ` Leo
2007-04-30 22:09 ` Richard Stallman
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=m3tzuycgml.fsf@kurono.home \
--to=joakim@verona.se \
--cc=emacs-devel@gnu.org \
--cc=lennart.borgman@gmail.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.