From: Christian Ohler <ohler+emacs@fastmail.net>
To: Lennart Borgman <lennart.borgman@gmail.com>
Cc: "Stephen J. Turnbull" <stephen@xemacs.org>,
Sebastian Rose <sebastian_rose@gmx.de>,
Chong Yidong <cyd@stupidchicken.com>,
Stefan Monnier <monnier@iro.umontreal.ca>,
emacs-devel Mailinglist <emacs-devel@gnu.org>
Subject: Re: testing framework and package.el
Date: Wed, 13 Oct 2010 01:36:04 +1100 [thread overview]
Message-ID: <4CB47254.7000904@fastmail.net> (raw)
In-Reply-To: <AANLkTi=xjLcXS-3aF6Ab-uuBTzv6h-SBB85T+sMjaLZR@mail.gmail.com>
On 12/10/10 20:41, Lennart Borgman wrote:
> Is there any other way supporting backward
> compatibility of the test than actually running them from time to time
> in older versions?
Rather than running the tests of Emacs version N in historical versions
before N, we can run them in future versions after N. This is actually
what happens naturally as the code evolves (assuming we run "make check"
regularly), so it's very simple and requires no added effort. (Of
course, this doesn't work for tests written after the fact.) As long as
we don't touch a given test, we know that it's compatible. If we have
to modify it to keep it passing, we know that there was an incompatible
change.
Christian.
next prev parent reply other threads:[~2010-10-12 14:36 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-27 15:18 testing framework and package.el Sebastian Rose
2010-09-27 22:57 ` Stefan Monnier
2010-09-27 23:42 ` Sebastian Rose
2010-09-27 23:55 ` Sebastian Rose
2010-10-01 13:01 ` Christian Ohler
2010-10-02 3:53 ` Sebastian Rose
2010-10-03 10:51 ` Christian Ohler
2010-10-03 20:52 ` Sebastian Rose
2010-10-04 15:36 ` Christian Ohler
2010-10-04 16:48 ` Chong Yidong
2010-10-05 1:17 ` Christian Ohler
2010-10-05 1:38 ` Lennart Borgman
2010-10-05 1:50 ` Sebastian Rose
2010-10-05 3:31 ` Christian Ohler
2010-10-05 4:39 ` Stephen J. Turnbull
2010-10-05 16:43 ` Eric Schulte
2010-10-05 23:18 ` Stefan Monnier
2010-10-11 9:26 ` Christian Ohler
2010-10-12 3:02 ` Stephen J. Turnbull
2010-10-12 9:41 ` Lennart Borgman
2010-10-12 13:39 ` Stephen J. Turnbull
2010-10-12 16:28 ` Lennart Borgman
2010-10-12 17:37 ` Stephen J. Turnbull
2010-10-12 17:54 ` Lennart Borgman
2010-10-13 0:36 ` Stefan Monnier
2010-10-13 9:03 ` Stephen J. Turnbull
2010-10-13 10:00 ` Christian Ohler
2010-10-13 14:19 ` Stephen J. Turnbull
2010-10-17 6:37 ` Christian Ohler
2010-10-17 14:54 ` Stefan Monnier
2010-10-18 6:55 ` Stephen J. Turnbull
2010-10-12 14:36 ` Christian Ohler [this message]
2010-10-12 17:41 ` Stephen J. Turnbull
2010-10-13 10:00 ` Christian Ohler
2010-10-13 14:13 ` Stephen J. Turnbull
2010-10-17 6:37 ` Christian Ohler
2010-10-12 14:19 ` Christian Ohler
2010-10-12 17:58 ` Stephen J. Turnbull
2010-10-12 18:13 ` Lennart Borgman
2010-10-13 10:00 ` Christian Ohler
2010-10-04 17:22 ` Eric Schulte
2010-10-05 0:01 ` Sebastian Rose
2010-10-04 13:02 ` Masatake YAMATO
2010-10-05 3:29 ` 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=4CB47254.7000904@fastmail.net \
--to=ohler+emacs@fastmail.net \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=lennart.borgman@gmail.com \
--cc=monnier@iro.umontreal.ca \
--cc=sebastian_rose@gmx.de \
--cc=stephen@xemacs.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).