lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Policy about not-yet-regression tests?


From: David Kastrup
Subject: Re: Policy about not-yet-regression tests?
Date: Sun, 10 Apr 2011 17:26:49 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux)

Graham Percival <address@hidden> writes:

> On Sun, Apr 10, 2011 at 08:35:54AM +0200, David Kastrup wrote:
>> We have a standard problem "bugfix should have regtest" which is not
>> working all too well.  If the responsibilities for bugfix and regtest
>> get decoupled, this might help.  After all, most bug reports already
>> require a demonstration to get accepted, and this demonstration will
>> often serve perfectly well as such a test.  Getting it into Lilypond
>> tells the bug reporter "something has been taken seriously".
>
> I do not think that this is an appropriate time to discuss changes
> to the bug squad policies, nor to our regtest organization.
> Please add an item to the GOP policy list about this, and we will
> discuss it in full in due course.

>From CG:

       Regression tests are added when new functionality is added to
    LilyPond.  They are also added when bugs are identified.  The
    snippet that causes the bug becomes a regression test to verify that
    the bug has been fixed.

Could you explain what the second sentence is supposed to mean?

-- 
David Kastrup




reply via email to

[Prev in Thread] Current Thread [Next in Thread]