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, bu
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
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
> > >t
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 -RELEAS
