[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: Stress Testing and QA before release
From:       Cristian Tibirna <tibirna () kde ! org>
Date:       2002-03-12 4:06:15
[Download RAW message or body]

On Monday 11 March 2002 22:32, Neil Stevens wrote:
> On Monday March 11, 2002 10:38, Dirk Mueller wrote:
> > On Mon, 11 Mär 2002, Chris Howells wrote:
> > > With the growing popularity of KDE, IMHO it's becoming more important
> > > to test things _fully_ before release. This is what the release
> > > candidates are here for of course, but with 3.0 at least the release
> > > candidates are probably not being used as much as they could be
> > > because we are not waiting 3 weeks (the right desciscion, I think) for
> > > the packagers to create binaries.
> >
> > Well, the time you waste in creating a collection of QA testcases you
> > could invest in actually doing the testing, which is for sure more fun
> > as well ;-)
>
> Yeah, but if he does this once, it will allow 200 others to walk through
> the tests easily, getting quality testing done in 200 x the situations.

Predetermined QA testing on GUI tends to be in-effective (captures a small 
number of all present problems) and much more volunteer-killing (tedious and 
non-selfishness-rewarding). If anybody wants to do some, excellent. But there 
is a major probability that efforts to develop QA tests be unsuccessful (by 
their very nature) and this will simply alienate testers.

CT
[prev in list] [next in list] [prev in thread] [next in thread]