Han-Wen Nienhuys <[email protected]> writes: > On Fri, Apr 8, 2011 at 11:01 AM, David Kastrup <[email protected]> wrote: >> do we just want regression tests for things that _do_ work currently, >> or is it ok to add tests for things that _should_ work but don't, as >> long as the test does not bomb out? > > I think adding things that don't work is not a good idea; it will > confuse people, and add noise for developers. We have the bug tracker > to keep track of feature requests.
Removing a bug is not the same as adding a feature. >> changes. Adding regression tests early can also mean that bug >> reports that get cured by independent work get noticed instead of >> remaining open. > > Almost all bugfixes should be accompanied by a regtest; if they are > not Graham's police should start hunting down offenders. I am talking about bugs without a fix. Sometimes they disappear as a sideeffect of fixing a different bug, or restructuring code. -- David Kastrup _______________________________________________ lilypond-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/lilypond-devel
