From: Eli Zaretskii <eliz@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: call for more ert tests
Date: Mon, 24 Jun 2013 21:21:50 +0300 [thread overview]
Message-ID: <838v1zjrnl.fsf@gnu.org> (raw)
In-Reply-To: <t3li5z76ux.fsf@fencepost.gnu.org>
> From: Glenn Morris <rgm@gnu.org>
> Date: Mon, 24 Jun 2013 13:31:50 -0400
>
> One thing that could help reduce this is more unit tests.
> If you haven't used it, ERT makes it pretty easy to write tests.
> Of course, many aspects of Emacs's behaviour are not easy to test (GUI
> stuff, etc.), but many are. See test/automated/ for examples. [2]
>
> For example, package.el seems like something that should have a test
> suite.
>
> So if you fix a bug, please consider adding a unit test to make sure it
> does not come back. Or if you rewrite a lisp package, consider adding
> tests at the same time to check that obvious functionality still works.
>
> I know writing tests is maybe not as interesting as writing shiny new
> features, but I think it will save work in the long run.
IMO, unless we require every new feature to come with a test and a
report that no regressions were found by running the existing tests,
we will never get any better testability than what we have now.
next prev parent reply other threads:[~2013-06-24 18:21 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-24 17:31 call for more ert tests Glenn Morris
2013-06-24 18:21 ` Eli Zaretskii [this message]
2013-06-24 18:24 ` Lennart Borgman
2013-07-01 11:35 ` Andreas Röhler
2013-07-01 16:14 ` Stefan Merten
2013-07-01 16:35 ` Andreas Röhler
2013-07-01 16:37 ` Eli Zaretskii
2013-07-01 17:35 ` Eli Zaretskii
2013-07-01 18:44 ` Stephen J. Turnbull
2013-07-01 19:32 ` Eli Zaretskii
2013-07-01 20:34 ` Dmitry Gutov
2013-06-24 18:33 ` Sebastian Wiesner
2013-06-24 18:40 ` Eli Zaretskii
2013-06-24 18:55 ` Sebastian Wiesner
2013-06-24 19:16 ` Eli Zaretskii
2013-06-24 19:20 ` Lennart Borgman
2013-06-24 19:35 ` Óscar Fuentes
2013-06-24 19:59 ` John Wiegley
2013-06-25 1:21 ` Leo Liu
2013-06-25 2:44 ` John Wiegley
2013-06-25 3:02 ` Stefan Monnier
2013-06-25 2:31 ` Stephen J. Turnbull
2013-06-25 14:38 ` Eli Zaretskii
2013-06-25 11:06 ` Lars Magne Ingebrigtsen
2013-06-25 12:11 ` Juanma Barranquero
2013-06-25 15:15 ` Eli Zaretskii
2013-06-25 19:18 ` Lars Magne Ingebrigtsen
2013-06-25 20:12 ` Eli Zaretskii
2013-06-25 20:36 ` Sebastian Wiesner
2013-06-25 20:44 ` Lars Magne Ingebrigtsen
2013-06-28 15:01 ` Ted Zlatanov
2013-06-28 15:39 ` Juanma Barranquero
2013-06-28 15:41 ` Dmitry Gutov
2013-06-26 9:03 ` Julien Danjou
2013-06-26 5:12 ` Stephen J. Turnbull
2013-06-24 19:46 ` Glenn Morris
2013-06-25 13:33 ` Noah Lavine
2013-06-25 17:18 ` Rüdiger Sonderfeld
2013-06-25 18:53 ` Eli Zaretskii
2013-06-25 20:29 ` Dmitry Gutov
2013-07-01 11:45 ` Andreas Röhler
2013-07-01 12:43 ` Ted Zlatanov
2013-07-01 14:13 ` Andreas Röhler
2013-06-24 18:29 ` David Engster
2013-06-24 18:38 ` Glenn Morris
2013-06-24 19:04 ` David Engster
2013-06-25 22:15 ` Daniel Hackney
2013-06-26 9:22 ` Stefan Merten
2013-06-26 12:17 ` Bozhidar Batsov
2013-06-26 15:52 ` Eli Zaretskii
2013-06-26 16:03 ` Bozhidar Batsov
2013-06-26 16:22 ` Eli Zaretskii
2013-06-26 19:01 ` Dmitry Gutov
2013-06-26 19:10 ` Michael Albinus
2013-06-26 19:34 ` Dmitry Gutov
2013-06-26 19:56 ` Michael Albinus
2013-06-26 19:28 ` Eli Zaretskii
2013-06-26 19:46 ` Teemu Likonen
2013-06-26 15:50 ` Eli Zaretskii
2013-06-29 15:11 ` Stefan Merten
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=838v1zjrnl.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rgm@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).