Date: Tue, 22 Oct 2002 00:01:27 +0100 From: Matthew Whelan <muttley@gotadsl.co.uk> To: "Fischer, Oliver" <plexus@snafu.de>, Chris BeHanna <behanna@zbzoom.net>, FreeBSD-Stable <stable@FreeBSD.ORG> Subject: Re: freebsd test matrix Message-ID: <20021021235512.C6F1.MUTTLEY@gotadsl.co.uk> In-Reply-To: <3DB3C877.7080904@snafu.de> References: <20021018134020.D8827-100000@fubar.adept.org> <3DB3C877.7080904@snafu.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 21 Oct 2002 11:27:19 +0200 "Fischer, Oliver" <plexus@snafu.de> wrote: > Mike Hoskins wrote: > > Clearly, this process indicates developers should write test cases for > > their code... Unfortuneately, the last thing an opensource project needs > > is more work for the developers. :) > > Yes, I know this argument but I think it isn't true. Only the start is > hard but if you have a working test system you are much more flexible > because you are not afraid that changes can break the system and you > don't realize it. I couldn't agree more. Testing discovers bugs at a faster rate than debugging, at least until the test becomes 'too big'. As a result, it actually *SAVES* developer time. If this weren't the case, noone would do it outside of safety-critical systems. The clever bit is knowing when to stop (ie. how big is too big). Starting should be a no-brainer. -- Matthew Whelan <muttley@gotadsl.co.uk> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021021235512.C6F1.MUTTLEY>