RE: QA testing: need to prove line by line

No offense meant.  In the QA sense, you are in production.  You write code
and develop systems--that's the product.  The idea is to avoid any
possibility of conflict of interest.  I'm sure you devote a lot of time to
trying to make sure that your code is error free, but there's no guarantee
that everyone feels the same way about their work.

It's important for the independence of the QA group that they develop their
own testing procedures.  It's also important that the QA group be
independent from managers with hot projects, although that's sometimes a
little harder to do. <g>

Formal QA might require that you follow a development procedure and sign a
document stating that you followed the spec, but the final testing should
not, in a perfect QA world, be your responsibility.

> -----Original Message-----
> From: Bale, Dan [mailto:D.Bale@handleman.com]
> Sent: Thursday, September 13, 2001 10:31 AM
> To: midrange-l@midrange.com
> Subject: RE: QA testing: need to prove line by line
>
>
> This is a multi-part message in MIME format.
> --
> [ Picked text/plain from multipart/alternative ]
> Did you misstate that?  Are you presuming I am in "production"?  As a
> developer, I haven't really thought of myself in that fashion.
>
> Anyway, FWIW, QA is just really starting up here.  We still have some
> managers that have hot projects that can't afford delays
> because of QA.
> It will be a slow, but deliberate, process.
>
> Dan Bale
> IT - AS/400
> Handleman Company
> 248-362-4400  Ext. 4952
> D.Bale@Handleman.com
>