Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!think.com!zaphod.mps.ohio-state.edu!ncar!noao!arizona!dave
From: dave@cs.arizona.edu (Dave P. Schaumann)
Newsgroups: comp.software-eng
Subject: Re: Code inspections
Message-ID: <795@caslon.cs.arizona.edu>
Date: 6 Feb 91 02:28:09 GMT
References: <14964@megatest.UUCP> <156342@felix.UUCP> <1991Jan31.151559.16415@bigsur.uucp> <1991Feb1.151945.22863@cs.uiuc.edu>
Organization: U of Arizona CS Dept, Tucson
Lines: 20

In article <1991Feb1.151945.22863@cs.uiuc.edu> marick@cs.uiuc.edu (Brian Marick) writes:
>[...]
>I apply the inspection checklist to look for those kinds of faults I
>expect the other tests won't catch.  Then I run the tests and add new
>ones until I've satisfied branch, loop, multi-condition, and weak
>mutation coverage.  

Forgive my ignorance, but what is "weak mutation coverage"?  Also, as long
as I'm asking basic questions, what is "regression testing"?  I've seen the
term in a few places, but I've never seen it defined, and a subject search
in the library turned up nothing.

>Brian Marick
>Motorola @ University of Illinois
>marick@cs.uiuc.edu, uiucdcs!marick

Thanks in advance.

Dave Schaumann		|  And then -- what then?  Then, future...
dave@cs.arizona.edu	|  		-Weather Report