Massive Konqueror Regression

[Wade Olson]

Was this a regression test of people's patience?  Did we fail?  What was 
the baseline?

Comprehensive automated testing tools are like code-writing code.  Great 
concepts for managers, not so much for those in the trenches.

According to gmail, it's taken 38 emails on this thread to go nowhere 
(#39 right here!).

Regression testing tools are imperative, but Plasma is a perfect example 
of new software that requires hard work and human scrutiny.

Put my name in the hat of human testing for 3.5 and 4.0 releases. 
(unless by human testing you mean avon and Mary Kay testing techniques)

Aaron J. Seigo wrote:

>On Wednesday 17 August 2005 06:37, David van Hoose wrote:
>  
>
>>Very true indeed. I helped out with testing KDE 2 and it was really fun,
>>but when KDE 3 beta came out, I couldn't spend as much time with it as
>>it needed because of all of the bugs. There needs to be a set of 
>>regressions that are run after developmental changes.
>>    
>>
>
>i feel like i'm talking to a brick wall here. we could have 10x the number of 
>regression tests we currently have and there would still be bugs that get 
>through. we need more people (e.g. not developers) doing q/a testing. i've 
>explained why a few times now, so tell me: what part of that explanation is 
>not clear enough?
>
>  
>
>------------------------------------------------------------------------
>
>_______________________________________________
>kde-quality mailing list
>kde-quality at kde.org
>https://mail.kde.org/mailman/listinfo/kde-quality
>  
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/kde-quality/attachments/20050818/205faf6d/attachment-0001.html