From: Eli Zaretskii <eliz@gnu.org>
To: "Przemysław Wojnowski" <esperanto@cumego.com>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH] CONTRIBUTE - writing tests for understanding internals
Date: Wed, 11 Nov 2015 23:26:07 +0200 [thread overview]
Message-ID: <83egfwjki8.fsf@gnu.org> (raw)
In-Reply-To: <5643AE61.1070503@cumego.com>
> From: Przemysław Wojnowski <esperanto@cumego.com>
> Date: Wed, 11 Nov 2015 22:08:49 +0100
> Cc: emacs-devel@gnu.org
>
> > The style is quite different: where CONTRIBUTE is about information
> > for contributors, the suggested change, with the exception of its
> > first sentence, is a motivational text that has no informational value
> > for contributors.
> I tend to agree that my style of writing is different than the rest of
> the document and is a place to improve. That's why I've sent it here.
I didn't object to your posting it here. You asked for a review, and
I tried to provide it.
> > More importantly, I disagree with your posit that writing tests is a
> > good way of learning about Emacs internals.
> Did you write this based on your experience?
Yes, of course. Why do you ask?
> It *is* very good way to learn about a project and, in many companies,
> is used to introduce new developers. (I do that every time and after
> sometime devs tell me that it is a good introduction, because project
> at the beginning were to big and overwhelming to them.)
Then I guess we will have to agree to disagree about this.
> > Best tests are written by looking at the spec alone,
> > because looking at the implementation will bias you when
> > you write the test. That's why tests should ideally be
> > written by someone who is not the implementor.
> Ideally yes. And new contributors are very close to this ideal, because
> they didn't implement the code and have docs as specs.
If they go by the spec and the docs, their tests will be very good, I
agree. But that's not an efficient way of learning the internals: for
that, you need to study the implementation, not the docs and the
requirements.
> > I'm sure you are
> > familiar with the TDD methodology, whose strong point is precisely
> > that you write tests before implementing anything.
> "Reality check:" we already have code base. ;-)
How does this argument help in advancing this discussion?
next prev parent reply other threads:[~2015-11-11 21:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-10 22:48 [PATCH] CONTRIBUTE - writing tests for understanding internals Przemysław Wojnowski
2015-11-10 22:58 ` John Wiegley
2015-11-11 3:36 ` Eli Zaretskii
2015-11-11 7:45 ` Przemysław Wojnowski
2015-11-11 8:26 ` Andreas Röhler
2015-11-11 15:40 ` Eli Zaretskii
2015-11-11 15:40 ` Eli Zaretskii
2015-11-11 21:08 ` Przemysław Wojnowski
2015-11-11 21:26 ` Eli Zaretskii [this message]
2015-11-11 21:36 ` John Wiegley
2015-11-12 3:40 ` Eli Zaretskii
2015-11-11 21:48 ` Przemysław Wojnowski
2015-11-12 7:16 ` Andreas Röhler
2015-11-12 16:15 ` Eli Zaretskii
2015-11-12 20:03 ` Stephen Leake
2015-11-12 20:40 ` Andreas Röhler
2015-11-12 20:55 ` Eli Zaretskii
2015-11-12 21:42 ` Przemysław Wojnowski
2015-11-13 7:33 ` Eli Zaretskii
2015-11-13 8:03 ` Andreas Röhler
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=83egfwjki8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=esperanto@cumego.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 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).