Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!pilchuck!dataio!fnx!nazgul!bright
From: bright@nazgul.UUCP (Walter Bright)
Newsgroups: comp.std.c
Subject: Re: Shipping bogus code
Message-ID: <134@nazgul.UUCP>
Date: 1 Nov 90 03:54:31 GMT
References: <27098@mimsy.umd.edu> <1990Oct22.231028.24623@zoo.toronto.edu> <18632@rpp386.cactus.org> <1990Oct24.173121.20610@druid.uucp> <116@raysnec.UUCP>
Reply-To: bright@nazgul.UUCP (Walter Bright)
Organization: Zortech, Seattle
Lines: 10

In article <116@raysnec.UUCP> shwake@raysnec.UUCP (Ray Shwake) writes:
<The same with software.  If you run a
<system utility and it immediately dumps core then you can safely say that
<someone didn't do their job.  If it dumps core only when run at the stroke
<of midnight then you can say it has a bug but you can understand why it
<wasn't caught by the testing group.

I am sometimes surprised at finding a major bug in a utility or library routine
and wonder why the test suite didn't catch it. Turns out that the *only* thing
that worked right was the *exact* test case. Sigh. Test suites are never done!