Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id <S132035AbRCVOsU>; Thu, 22 Mar 2001 09:48:20 -0500
Received: (majordomo@vger.kernel.org) by vger.kernel.org
	id <S132040AbRCVOsK>; Thu, 22 Mar 2001 09:48:10 -0500
Received: from chaos.analogic.com ([204.178.40.224]:42880 "EHLO
	chaos.analogic.com") by vger.kernel.org with ESMTP
	id <S132037AbRCVOrz>; Thu, 22 Mar 2001 09:47:55 -0500
Date: Thu, 22 Mar 2001 09:45:55 -0500 (EST)
From: "Richard B. Johnson" <root@chaos.analogic.com>
Reply-To: root@chaos.analogic.com
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
cc: nbecker@fred.net, linux-kernel@vger.kernel.org
Subject: Re: regression testing
In-Reply-To: <E14g6My-0002dw-00@the-village.bc.nu>
Message-ID: <Pine.LNX.3.95.1010322094517.21282A-100000@chaos.analogic.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org

On Thu, 22 Mar 2001, Alan Cox wrote:

> > Regression testing __is__ what happens when 10,000 testers independently
> > try to break the software!
> 
> Nope. Thats stress testing and a limited amount of coverage testing.
> 
> > Canned so-called "regression-test" schemes will fail to test at least
> > 90 percent of the code paths, while attempting to "test" 100 percent
> > of the code!
> 
> Then they are not well designed. Tools like gprof and the kernel profiling
> will let you measure code path coverage of a test series
> 

Alan's back! 

Cheers,
Dick Johnson

Penguin : Linux version 2.4.1 on an i686 machine (799.53 BogoMips).

"Memory is like gasoline. You use it up when you are running. Of
course you get it all back when you reboot..."; Actual explanation
obtained from the Micro$oft help desk.


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/