HP3000-L Archives

October 2001, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Steve Dirickson (Volt)" <[log in to unmask]>
Reply To:
Steve Dirickson (Volt)
Date:
Tue, 23 Oct 2001 18:57:19 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (11 lines)
> The other thing that is/should be done alongside regression 
> testing is 'path
> flow analysis'. This verifies that a high percentage of the 
> logic branches
> have been exercised in the test sequence.

Though it's important to recognize that coverage testing, either line coverage or branch coverage, isn't going to come anywhere near detecting all the defects in the code. Kaner cites Beizer's estimate that complete coverage, i.e. taking every possible path out of every branch point, will detect--at best--half the defects.

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2