unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Artur Malabarba <bruce.connor.am@gmail.com>
To: emacs-devel <emacs-devel@gnu.org>
Subject: Which files suffer from a complete lack of tests?
Date: Tue, 27 Oct 2015 23:28:46 +0000	[thread overview]
Message-ID: <CAAdUY-+e5kugqLi6-dTWesw_9L56FibWUCzexdRPdJX2SrL_fA@mail.gmail.com> (raw)
In-Reply-To: <CAAdUY-KDQ+V0Zgj4gvgi9bxf5A+O5guNw+M3042w4Qtz_55j=A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 803 bytes --]

I'm trying to add some tests for features (.el source files) that are
completely devoid of them. So I welcome suggestions of elisp files that
have no tests whatsoever. I also welcome volunteers to help, of course.

Context:
Besides the fact that tests are a good idea, I think that having features
with no test file at all is measurably worse than having just one or two
tests.

When a source file has no corresponding test file, someone contributing to
it feels perfectly entitled to not create one. What's worse, even if they
did want to add a test, there's a chance they might be discouraged by this,
specially if they weren't yet sure how to implement the test.

So it is my opinion that adding tests to these unfortunate files would
provide a bit more benefit for the effort invested.

Best,
Artur

[-- Attachment #2: Type: text/html, Size: 925 bytes --]

       reply	other threads:[~2015-10-27 23:28 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAAdUY-KDQ+V0Zgj4gvgi9bxf5A+O5guNw+M3042w4Qtz_55j=A@mail.gmail.com>
2015-10-27 23:28 ` Artur Malabarba [this message]
2015-10-27 23:31   ` Which files suffer from a complete lack of tests? John Wiegley
2015-10-28 16:02   ` Eli Zaretskii
2015-10-28 19:20   ` Michael Albinus
2015-10-28 20:15     ` Artur Malabarba
2015-10-29  7:46       ` Michael Albinus
2015-11-07 19:13         ` Michael Albinus
2015-11-07 19:26           ` You probably need a new maintainer for vc.el Eric S. Raymond
2015-11-08  1:06           ` Which files suffer from a complete lack of tests? Kelvin White
2015-11-08  2:18             ` Artur Malabarba
2015-11-08  9:48             ` Michael Albinus
2015-11-08  2:16           ` Artur Malabarba
2015-11-08  2:26             ` Dmitry Gutov
2015-11-08  2:28           ` Dmitry Gutov
2015-11-08  8:41             ` Michael Albinus
2015-11-08 11:45               ` Dmitry Gutov
2015-11-08 12:30                 ` Michael Albinus
2015-10-29  1:13     ` Dmitry Gutov
2015-10-29  7:48       ` Michael Albinus

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=CAAdUY-+e5kugqLi6-dTWesw_9L56FibWUCzexdRPdJX2SrL_fA@mail.gmail.com \
    --to=bruce.connor.am@gmail.com \
    --cc=emacs-devel@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).