public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Cort Dougan <cort@fsmlabs.com>
To: "Richard B. Johnson" <root@chaos.analogic.com>
Cc: nbecker@fred.net, linux-kernel@vger.kernel.org
Subject: Re: regression testing
Date: Thu, 22 Mar 2001 11:18:42 -0700	[thread overview]
Message-ID: <20010322111842.C17926@hq.fsmlabs.com> (raw)
In-Reply-To: <x88zoeeeyh8.fsf@adglinux1.hns.com> <Pine.LNX.3.95.1010322083448.20107C-100000@chaos.analogic.com>
In-Reply-To: <Pine.LNX.3.95.1010322083448.20107C-100000@chaos.analogic.com>; from root@chaos.analogic.com on Thu, Mar 22, 2001 at 08:39:06AM -0500

} On 22 Mar 2001 nbecker@fred.net wrote:
} 
} > Hi.  I was wondering if there has been any discussion of kernel
} > regression testing.  Wouldn't it be great if we didn't have to depend
} > on human testers to verify every change didn't break something?
} > 
} > OK, I'll admit I haven't given this a lot of thought.  What I'm
} > wondering is whether the user-mode linux could help here (allow a way
} > to simulate controlled activity).
} > -
} 
} Regression testing __is__ what happens when 10,000 testers independently
} try to break the software!

No, in fact that is not a regression test.

} 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!

A canned set of regression tests would actually do what they're supposed to
- prevent the kernel from regressing.  If you fix a bug - write a test for
that bug and keep running it.  Something we follow for RTLinux that has
helped us immensely.

  parent reply	other threads:[~2001-03-22 18:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-22 13:15 regression testing nbecker
2001-03-22 13:39 ` Richard B. Johnson
2001-03-22 13:47   ` nbecker
2001-03-22 14:47   ` Alan Cox
2001-03-22 14:45     ` Richard B. Johnson
2001-03-22 18:18   ` Cort Dougan [this message]
2001-03-22 15:13 ` Wade Hampton
2001-03-22 15:56   ` Nathan Straz
2001-03-22 16:46     ` Nathan Dabney
2001-03-22 16:37 ` Rik van Riel
2001-03-22 18:21   ` Cort Dougan
2001-03-22 18:12 ` Jonathan Morton
2001-03-23 15:00   ` Horst von Brand
2001-03-23 15:29     ` Rik van Riel
2001-03-23 10:11 ` Eric W. Biederman
2001-03-27  7:21   ` Werner Almesberger
  -- strict thread matches above, loose matches on Subject: below --
2001-03-22 18:44 Torrey Hoffman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010322111842.C17926@hq.fsmlabs.com \
    --to=cort@fsmlabs.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nbecker@fred.net \
    --cc=root@chaos.analogic.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox