unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
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: Thu, 29 Oct 2015 08:46:06 +0100	[thread overview]
Message-ID: <874mhaw20x.fsf@gmx.de> (raw)
In-Reply-To: <CAAdUY-+RJax8PHJahOYHARz8BJcfvCM4xuoa4fqbcn3Vgeahdw@mail.gmail.com> (Artur Malabarba's message of "Wed, 28 Oct 2015 20:15:56 +0000")

Artur Malabarba <bruce.connor.am@gmail.com> writes:

> On 28 Oct 2015 7:20 pm, "Michael Albinus" <michael.albinus@gmx.de>
> wrote:
>> Last year, I've started to write vc-tests.el. I have not enough
>> knowledge about vc to do it on my own, but I was enouraged by Eric
>> Raymond to do so. Unfortunately, he stopped to support me after a while,
>> so the work is stalled since then.
>
> Still, did you get to push this partial progress? 

Everything which I had done that time is pushed to the repo.

>> If somebody with more knowledge about vc than me would join that work, I
>> would be willing to continue. Could you help me with this? Other
>> volunteers?
>
> I'm not a user of vc, but let us know your questions, maybe I can help
> with some. Or maybe a vc user will jump in (this list is full of them ;
> -). Really, don't be afraid to ask.

Will do.

>> In parallel, it might be useful to work on Bug#19548. As Glenn said, the
>> documentation lacks the changes which have been applied last year.
>
> Documentation is certainly another good way to help.

In this case it is important, because the behaviour of the functions
differ sometimes from what is documented, and I'm uncertain whom to
believe when asserting the test results. For the time being I have
accepted most of the results (modulo some few obvious errors, which I
did fix in vc-*.el), but maybe the checks are too weak, and there are
still some problems in vc-*.el, which are uncovered by this strategy of
vc-tests.el.

Best regards, Michael.



  reply	other threads:[~2015-10-29  7:46 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
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 [this message]
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=874mhaw20x.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --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).