Re: freebsd test matrix

2002-10-18 Thread Ricardo Anguiano
Chris BeHanna [EMAIL PROTECTED] writes:

 The thing that bites you in the butt is test harnesses.
 Invariably, the commonly-available (free) harnesses will lack
 features desired by the QA team; therefore, they end up rolling
 their own.  In a volunteer project like this, that's a big, but
 necessary, first step to take.

Has anyone here tried QMTest?

http://www.codesourcery.com/qm/qmtest

I might be able to convince management that it's a good idea to work
on FreeBSD testing.  Is there any interest?  Who would I contact
(qa@freebsd?) to figure this out and try to get started?

-- 
Ricardo Anguiano
CodeSourcery, LLC

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message



Re: freebsd test matrix

2002-10-17 Thread Fischer, Oliver

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


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message



Re: freebsd test matrix

2002-10-16 Thread David Kleiner

On Wed, Oct 16, 2002 at 11:03:21PM +0200, Fischer, Oliver wrote:
 Mike Hoskins wrote:
 Hmm, I wonder if something similar is used or was developed for internal
 QA?  Anyone?  It seems like there should at least be a best practice for
 testing systems...  How do we currently make a -RELEASE with confidence?
 Of course you can't verify a given release builds on every platform, but
 is there an automated means of verifying system compoents work and
 interoperate properly on a given test system or set of systems?
 
 
 http://martinfowler.com/articles/continuousIntegration.html
 
 
 
 

Hi,

In a commercial world, there is a lot of pre-integration QA testing going on - 
question is, where do you start?  What test harness you want to use?  Which
test suites?  Are you interested in standards (posix and such), ABI, 
stress testing, library testing, fs testing, interoperability and so on?

Just my 2 cents,

David

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message



Re: freebsd test matrix

2002-10-16 Thread Chris BeHanna

On Wed, 16 Oct 2002, David Kleiner wrote:

 On Wed, Oct 16, 2002 at 11:03:21PM +0200, Fischer, Oliver wrote:
  Mike Hoskins wrote:
  Hmm, I wonder if something similar is used or was developed for internal
  QA?  Anyone?  It seems like there should at least be a best practice for
  testing systems...  How do we currently make a -RELEASE with confidence?
  Of course you can't verify a given release builds on every platform, but
  is there an automated means of verifying system compoents work and
  interoperate properly on a given test system or set of systems?
 
  http://martinfowler.com/articles/continuousIntegration.html

 In a commercial world, there is a lot of pre-integration QA testing
 going on - question is, where do you start?  What test harness you
 want to use?  Which test suites?  Are you interested in standards
 (posix and such), ABI, stress testing, library testing, fs testing,
 interoperability and so on?

All of the above, in bite-sized, doable chunks.

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.

-- 
Chris BeHanna  http://www.pennasoft.com
Principal Consultant
PennaSoft Corporation
[EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message