From: phillip.lord@russet.org.uk (Phillip Lord)
To: "Przemysław Wojnowski" <esperanto@cumego.com>
Cc: emacs-devel@gnu.org
Subject: Re: burden of maintainance
Date: Fri, 02 Oct 2015 12:25:18 +0100 [thread overview]
Message-ID: <87si5t1pi9.fsf@russet.org.uk> (raw)
In-Reply-To: <560D60A1.4090909@cumego.com> ("Przemysław Wojnowski"'s message of "Thu, 1 Oct 2015 18:34:41 +0200")
Przemysław Wojnowski <esperanto@cumego.com> writes:
>> as the burden of maintainance was mentioned: from reading the
>> bug-reports got the impression, a more strict test-regime might reduce
>> that.
>>
>> If a bug shows up, the first question should be: how it could survive
>> the tests?
>
> +1
>
> In previous project I joined a team that couldn't do any release in 4
> years. I've introduced automated tests and refactoring among other
> things and after 2 years we were releasing 4 times a year, with 3 times
> less defects, found much sooner in release cycle and they were easier
> to fix.
>
> Some people here work in academia so maybe don't have such experiences,
> but in software industry automated tests are a standard. Projects
> without (or with weak) tests are replaced with those having strong
> tests.
Well some of us work in academia and still have this experience anyway,
which is why I write tests for most of my own Emacs packages.
WRT Emacs, I think, that testing would be a good thing but there are a
couple of hurdles to overcome. First, most of Emacs doesn't have tests,
simply because it predates widespread use of testing. Secondly, Emacs
use of global state (current-buffer!) can make testing quite difficult;
combined with the reality that some of the functions are pretty large,
and will be difficult to retrofit tests onto, I think this is quite an
issue. And, thirdly, testing of interactive programs is difficult
anyway; the difficulty of writing tests in this environment is much
higher, and the payback lower.
We can have more than one maintainer. Someone who wanted to just
concentrate on getting a nightly build infrastructure running, with
email to emacs-diffs, and then starting to add fixtures and some other
frameworks to ert would be valuable addition to the process.
Phil
next prev parent reply other threads:[~2015-10-02 11:25 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-01 8:10 burden of maintainance Andreas Röhler
2015-10-01 16:03 ` Eli Zaretskii
2015-10-01 18:46 ` Andreas Röhler
2015-10-01 19:09 ` Eli Zaretskii
2015-10-01 20:18 ` Andreas Röhler
2015-10-01 20:27 ` Eli Zaretskii
2015-10-02 13:54 ` Przemysław Wojnowski
2015-10-02 14:15 ` Eli Zaretskii
2015-10-02 17:18 ` Tassilo Horn
2015-10-02 18:24 ` Eli Zaretskii
2015-10-02 18:47 ` joakim
2015-10-02 19:16 ` Tassilo Horn
2015-10-02 20:53 ` Eli Zaretskii
2015-10-02 19:28 ` Chad Brown
2015-10-02 7:51 ` Helmut Eller
2015-10-02 8:47 ` Eli Zaretskii
2015-10-02 8:56 ` Helmut Eller
2015-10-02 8:59 ` Eli Zaretskii
2015-10-02 11:46 ` Michael Albinus
2015-10-02 11:58 ` Phillip Lord
2015-10-02 13:14 ` Artur Malabarba
2015-10-02 13:36 ` Eli Zaretskii
2015-10-02 15:00 ` Andreas Röhler
2015-10-02 15:16 ` Eli Zaretskii
2015-10-02 17:19 ` Andreas Röhler
2015-10-02 18:08 ` Eli Zaretskii
2015-10-02 18:54 ` Andreas Röhler
2015-10-02 20:39 ` Tassilo Horn
2015-10-03 6:53 ` Andreas Röhler
2015-10-03 7:31 ` Tassilo Horn
2015-10-03 1:38 ` Richard Stallman
2015-10-03 0:38 ` Eric Ludlam
2015-10-02 23:24 ` Xue Fuqiao
2015-10-03 6:42 ` Przemysław Wojnowski
2015-10-03 7:00 ` Xue Fuqiao
2015-10-03 7:15 ` Eli Zaretskii
2015-10-01 16:34 ` Przemysław Wojnowski
2015-10-02 11:25 ` Phillip Lord [this message]
2015-10-02 12:27 ` Michael Albinus
2015-10-02 14:53 ` Phillip Lord
2015-10-02 16:56 ` Michael Albinus
2015-10-03 1:35 ` Richard Stallman
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=87si5t1pi9.fsf@russet.org.uk \
--to=phillip.lord@russet.org.uk \
--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).