Re: proving a bug is gone
- To: debian-policy@lists.debian.org
- Subject: Re: proving a bug is gone
- From: Manoj Srivastava <srivasta@datasync.com>
- Date: 08 Nov 1998 23:57:13 -0600
- Message-id: <[🔎] 87ww55h0hy.fsf@tiamat.datasync.com>
- In-reply-to: Adam Di Carlo's message of "08 Nov 1998 16:17:37 -0500"
- References: <873e7x1k1i.fsf@tiamat.datasync.com> <74NzWXk1w-B@khms.westfalen.de> <873e7vzcf1.fsf@tiamat.datasync.com> <19981107204834.A18168@test.legislate.com> <87g1buyc44.fsf@tiamat.datasync.com> <19981108085023.A29304@test.legislate.com> <13893.42072.52083.946292@sonny.econ.queensu.ca> <19981108093001.U20906@test.legislate.com> <13893.45000.262027.553781@sonny.econ.queensu.ca> <19981108100627.W20906@test.legislate.com> <[🔎] oak915ope6.fsf_-_@burrito.fake>
Hi,
I have a package where I wrote a test suite. It is
pkg-order. I think I spent about a fifth of the total time creating
the package in writing the test suite. I don't think I could have
written the tests had I not also been the author of the package.
Writing regression tests for real is a hard, painstaking
effort, often requiring intimate knowledge of the code, and often
needs to be tied up with the code itself, changing as the source
changes.
Requiring test cases that check for all bugs is an impossible
burden. Encouraging tests, on the other had, is probably a good
idea.
manoj
--
Pick another fortune cookie.
Manoj Srivastava <srivasta@acm.org> <http://www.datasync.com/%7Esrivasta/>
Key C7261095 fingerprint = CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
Reply to: