From: "John Wiegley" <johnw@newartisans.com>
To: Artur Malabarba <bruce.connor.am@gmail.com>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Which files suffer from a complete lack of tests?
Date: Tue, 27 Oct 2015 16:31:26 -0700 [thread overview]
Message-ID: <m27fm728j5.fsf@newartisans.com> (raw)
In-Reply-To: <CAAdUY-+e5kugqLi6-dTWesw_9L56FibWUCzexdRPdJX2SrL_fA@mail.gmail.com> (Artur Malabarba's message of "Tue, 27 Oct 2015 23:28:46 +0000")
>>>>> Artur Malabarba <bruce.connor.am@gmail.com> writes:
> 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.
I'm inclined to agree, Artur. Thank you for starting this initiative.
John
next prev parent reply other threads:[~2015-10-27 23:31 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 ` Which files suffer from a complete lack of tests? Artur Malabarba
2015-10-27 23:31 ` John Wiegley [this message]
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=m27fm728j5.fsf@newartisans.com \
--to=johnw@newartisans.com \
--cc=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).