From owner-freebsd-stable Thu Oct 17 17:42:48 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E0AAB37B404 for ; Thu, 17 Oct 2002 17:42:42 -0700 (PDT) Received: from mail1.panix.com (mail1.panix.com [166.84.1.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2873143E65 for ; Thu, 17 Oct 2002 17:42:42 -0700 (PDT) (envelope-from kleiner@panix.com) Received: from panix5.panix.com (panix5.panix.com [166.84.1.5]) by mail1.panix.com (Postfix) with ESMTP id A50204885E; Thu, 17 Oct 2002 19:43:20 -0400 (EDT) Received: (from kleiner@localhost) by panix5.panix.com (8.11.6/8.8.8/PanixN1.0) id g9HNhKJ02937; Thu, 17 Oct 2002 19:43:20 -0400 (EDT) Date: Thu, 17 Oct 2002 19:43:20 -0400 From: David Kleiner To: "Fischer, Oliver" Cc: Chris BeHanna , FreeBSD-Stable Subject: Re: freebsd test matrix Message-ID: <20021017234320.GA1664@panix.com> References: <20021017005151.T771-100000@topperwein.dyndns.org> <3DAE6116.5080904@snafu.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3DAE6116.5080904@snafu.de> User-Agent: Mutt/1.4i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Oct 17, 2002 at 09:04:54AM +0200, Fischer, Oliver wrote: > Chris BeHanna wrote: > > > > I'm currently doing QA on a (very) large software project, and all > >of those things are important. Some of the testing uses existing > >industry test suites and benchmarking tools, and some of it (much of > >it) is custom. Being able to compile, install, and boot is just the > >tip of the iceberg. > > > > I agree, it is only the top of it. I have an idea how to do this for a > lot of programms, but no one how to do it with the more system specific. > Does anyone know how commercial os vendors do it? > > Bye > > Oliver > > As something I am involved with (not to mention any names) - and I don't know if any of it has been looked at in the open-source U*x world: nightly build cycles with basic (short stress, basic api sanity, some standards compliance) bi-weekly - more involved api, abi, stress, standards beta-candidates, release candidates and so on - even more longer-term test suites. As we, most likely, cannot use anything out of the Commercial World, all this has to be built from close to scratch. I may be wrong here but it is a likelier scenario. Ideas, anyone? David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message