Date: Thu, 17 Oct 2002 19:43:20 -0400 From: David Kleiner <kleiner@panix.com> To: "Fischer, Oliver" <plexus@snafu.de> Cc: Chris BeHanna <behanna@zbzoom.net>, FreeBSD-Stable <stable@freebsd.org> Subject: Re: freebsd test matrix Message-ID: <20021017234320.GA1664@panix.com> In-Reply-To: <3DAE6116.5080904@snafu.de> References: <20021017005151.T771-100000@topperwein.dyndns.org> <3DAE6116.5080904@snafu.de>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021017234320.GA1664>